Authorizations
You define authorizations to grant users the permissions to execute one or more permitted actions. The user can be an individual user, a group, or a role. In the ES Repository, you can define two types of authorizations: basic and advanced. The basic authorization allows you to assign simple actions such as read, write, delete, and so on, to users. However, if you want to assign granular permissions, you use the advanced authorizations.
Basic Authorizations
With basic authorizations, you can assign the following actions to users:
|
Action |
Description |
|
Edit Authorizations |
Modify the authorizations defined in the ES Builder |
|
Execute Reports |
Run reports on the Process Component Interaction Models, and assign usage profiles to users |
|
Write |
Create, modify, and delete objects |
Advanced Authorizations
Advanced authorization gives you the flexibility to assign granular permissions specific to roles. For example, for a developer working with service interfaces, you can provide permissions to only publish service interfaces.
With advanced authorizations, you can assign the following actions to users:
-
Publish service interfaces
-
Update underlying software component versions
-
Modify classifications
-
Create non-local software component versions
-
Take over change list
-
Generate Java proxy
-
Export
-
Import
-
Transfer
-
Write
-
Create children
-
Delete children
-
Edit children
-
Modify underlying objects
-
Edit folder
-
Delete folder
-
Edit object
-
Delete object
-
When you assign permissions to an object, only the appropriate actions from above takes effect.
To enable advanced authorizations, you should run the CTC template Configure Advanced Authorizations in ESR . For more information, see Configuring Advanced Authorizations .
Authorization Checks
In the ES Builder, you can define authorizations for objects, folders, namespaces, and software component versions. The system checks for authorizations based on hierarchy. The system first checks authorizations for objects. If no authorizations are defined for the object, it then checks authorizations for folders, then namespaces, and software component versions. If no authorizations are defined, the default authorizations defined for the repository takes effect. If authorizations are not defined in the repository, then the authorization checks are performed based on user defined roles. For more information, see Defining User Roles .