mkrolemap

Creates or updates a rolemap object

Applicability


Product	Command type
VersionVault	cleartool subcommand


Platform
UNIX
Linux
Windows

Synopsis

mkrolemap [ -set rolemap-file-pname ]: -policy policy-selector; [ -rolemap controlling-rolemap-selector ]; [ -c/omment comment | -cfi/le pname | -cq/uery | -cqe/ach | -nc/omment ]; rolemap-selector ...
mkrolemap -replace: [ -set rolemap-file-pname ]; [ -policy policy-selector ]; [ -rolemap controlling-rolemap-selector ]; [ -c/omment comment | -cfi/le pname | -cq/uery | -cqe/ach | -nc/omment ]; rolemap-selector ...

Description

The mkrolemap command creates or updates a rolemap object. Rolemap objects contain role-to-principal bindings; that is, they map user roles to the identities of principals.

Restrictions

Authorization

The principal must have the following permissions:

read-info on VOB object
mkrolemap on VOB object

For a mkrolemap -replace operation, the principal must also have read-name, read-info, mod-props on the target rolemap.

Locks

An error occurs if one or more of these objects are locked: VOB; and for a mkrolemap -replace operation, the target rolemap.

Mastership

(Replicated VOBs) For a mkrolemap -replace operation, the replica must master the target rolemap.

Options and arguments

Specifying the rolemap and policy

-set rolemap-file-pname

Pathname to the rolemap file that contains the role-to-principal bindings. For example:

Role: Administrator --> User:DOMAIN/albert
Role: Developer --> User:DOMAIN/bob

-policy policy-selector: The policy that is to be associated with the specified rolemap

rolemap-selector: The name or list of names for the rolemap that is about to be created; or, if used with -replace , the rolemap name of the existing rolemap that is to be redefined.

Updating a rolemap

-replace: Replaces the rolemap for the current rolemap-selector with the role bindings defined in the rolemap-file-pname. For all elements that are controlled by this rolemap object, the element versions and associated storage containers are reprotected (with native operating system file system ACLs) to implement the effective ACL of the new rolemap.

Event records and comments

Default: Creates one or more event records, with commenting controlled by your .versionvault_profile file (default: -cqe). See the comments reference page. Comments can be edited with chevent.
-c/omment comment | -cfi/le comment-file-pname |-cq/uery | -cqe/ach | -nc/omment: Overrides the default with the option you specify. See the comments reference page.

Examples

The UNIX system and Linux examples in this section are written for use in csh. If you use another shell, you might need to use different quoting and escaping conventions.

The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you might need to change the wildcards and quoting to make your command interpreter process the command appropriately.

In cleartool single-command mode, cmd-context represents the UNIX system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.

Create a rolemap.
cmd-context mkrolemap -set rolemap.acl -policy DefaultDevelopmentPolicy DevelopmentRolemap
Create an empty rolemap.
cmd-context mkrolemap -policy DefaultDevelopmentPolicy DevelopmentRolemap