permissions
Identity checking
DESCRIPTION
In general, only commands that modify
(write to) a VOB or a project VOB are subjected to identity checking. The
following hierarchy of identity checking is used, in a command-specific manner,
to determine whether a command can proceed or be canceled:
Both file system and non-file-system
objects have an owner and a group; this information is stored with the object.
When an object is created, its owner and group are set to that of the user
who created it. Use the protect command
to change the owner (–chown) or group (–chgrp)
of the object. The describe command displays
the owner and group of the object.
The scheduler maintains its own access
control list (ACL), which determines who is allowed access to the scheduler
and to the ACL itself. See the schedule reference
page for more information.
The reference page for a command lists
the special identities (if any) required to use the command along with other
restrictions on its use.
The sections below list all cleartool subcommands, categorized by their identity
requirements. For information about identity checking for ClearCase and ClearCase LT
commands (that is, other than cleartool subcommands),
see the corresponding reference pages.
one of: element group member, element owner, VOB owner, root, member
of the ClearCase administrators group, local administrator of the ClearCase LT
server host; (for commands that operate on objects) object group member, object
owner, VOB owner, root, member of the ClearCase administrators group, local
administrator of the ClearCase LT server host
one of: version creator, element owner, VOB owner, root, member of
the ClearCase administrators group, local administrator of the ClearCase LT
server host
one of: element owner, VOB owner, root, member of the ClearCase administrators
group, local administrator of the ClearCase LT server host
one of: user associated with event, object owner, VOB owner, root,
member of the ClearCase administrators group, local administrator of the ClearCase LT
server host
chevent
one of: branch creator, element owner, VOB owner, root, member of the
ClearCase administrators group, local administrator of the ClearCase LT
server host
one of: type owner, VOB owner, root, member of the ClearCase administrators
group, local administrator of the ClearCase LT server host
one of: pool owner, VOB owner, root, member of the ClearCase administrators
group
one of: DO group member, DO owner, VOB owner, root, member of the ClearCase
administrators group
rmdo
Note: Only
the VOB owner and root, members of the ClearCase
administrators group can delete a shared derived object.
one of: view owner, root, member of the ClearCase administrators group,
local administrator of the ClearCase LT server host
one of: owner, VOB owner, root, member of the ClearCase administrators
group, local administrator of the ClearCase LT server host
one of: owner, project VOB owner, root, member of the ClearCase administrators
group, local administrator of the ClearCase LT server host
one of: owner, stream owner, root, member of the ClearCase administrators
group, local administrator of the ClearCase LT server host
one of: owner, VOB owner, root, member of the ClearCase administrators
group
one of: VOB owner, root, member of the ClearCase administrators group
one of: VOB owner, root, member of the ClearCase administrators group,
local administrator of the ClearCase LT server host
VOB owner
mktag (private
VOB tag) mount (private VOB)
view owner
chview (can
also be root on view server host)
root, member of the ClearCase administrators group, local administrator
of the ClearCase LT server host
root, local administrator of the ClearCase VOB server host, local administrator
of the ClearCase LT server host
same permissions as those for creating the corresponding type object
cptype
permissions controlled by the scheduler ACL
SEE ALSO
Reference pages for individual commands