A role in CzechIdM is an entity representing a set (1 or many) of permissions/privileges on the end system or in CzechIdM itself. Users acquire roles:

• automatically – according to the organizational placement of the identity, identity or contract attributes
• manually – through assigning based on the user’s request in the CzechIdM self-service or by a CzechIdM administrator.
• by business role - roles (sub) can be assigned automatically, when other role (superior) by defined role composition is assigned manually or by some automatic role.

From the perspective of the identity manager, it does not matter whether the user acquires an account in a specific application, is placed in a group in LDAP, his indication is set to “can use VPN”, or a permission is set for him in the application. In all the cases, a role is assigned. A simplification carried out like this allows general rules to be applied for assigning all types of permissions (~roles) in the same way.

…to be completed

Roles are assigned to users via their contracts. If a contract is not valid (time validity) the roles on the contract are removed. In other words, the identity loses roles permissions in IdM and rights in connected systems.

Role with the same base code could be created from / for different environment. Final role code is combined from the base code and environment identifier. When role is created (or synchronized), then role attributes can be used:

• baseCode - base code without environment. If environment is not used, then baseCode value is the same as code value, e.g. roleOne
• environment - environment identifier, e.g. dev.
• code - complex code. If environment is not used, then baseCode value is the same as code value, otherwise complex code is combined from base code, environment and joined with separator (| by default). For example roleOne|dev.

Role permissions define rights for administrator actions in CzechIdM. A permission for CzechIdM is not necessarily defined for every role. A permission is, for example, READ on USERS. A user having a role with this specific permission can see the read-only detail of all identities in CzechIdM.

The level of criticality can be set for every role. Criticality denotes, who approves its assignment. Role can have criticality from 0 to 5.

Business roles (composition) can be defined on role detail. Business role could contain sub roles - all sub roles are assigned automatically, when business role is assigned to identity. Sub roles has the same validity as business role. When assigned business role is removed from identity, then all sub roles are removed automatically too. Sub roles are processed on the background asynchronously (by processors), only business roles (⇒ direct roles) are assigned synchronously. Sub roles defined by business roles are recalculated on the background (by long running tasks), when business role definition is created or removed - sub roles are assigned to identities, which already owns business (or any superior) role.

Segregation of Duties (SoD) can be ensured by incompatible roles. Their setup resembles that of business roles, described above.

The old generation CzechIdM used to have a feature of Role's incompatibility. By incompatibility we mean that you can set restrictions on roles A and B that will stop any user or process from assigning these two roles to the same user at once. In the new generation CzechIdM, we now have a similar feature. The difference is, however, that our experience of CzechIdM deployments on projects have taught us that users prefer this incompatibility function to work merely as a soft mechanism. In other words, CzechIdM will allow a user (identity) to have incompatible roles as long as an administrator/security manager is notified about this incident. The security staff also get a new tool to generate a special report, listing all users with incompatible roles - the report is prepared in the reports module named Identities-assigned incompatible roles.

When an incompatible role has been assigned to an identity, a warning stating the incompatible role definition is shown.

The same warning symbol is shown when an identity requests new role(s) which happen to be incompatible with one of the subroles nested within a business role composition. In this case, the informative symbol is ALSO shown next to a business role that IS NOT itself incompatible with the requested role.

In other words, the meaning of the symbol is somewhat different then: it does not mean the respective role - marked by this symbol - is incompatible, but rather it serves as an indication that one of the subroles down the business role cascade is incompatible.

… to be completed

The role can be linked to a Tree structure (e.g. position in organizational structure). That role is assigned to and removed from a user based on adding/removing the user (via their contract or other contract position) to/from the organizational tree structure. If a contract is not valid yet, roles are assigned but are disabled until the contract starts.

The role can be also linked with value in attribute (value can be stored in Identity, Identity extended attribute, Contract and Contract extended attribute). That role is assigned to and removed from a user based on the value in the specific attribute. Recalculating of this automatic roles is done after saving identity, identity extended attribute attributes, contract and contract extended attribute attributes. All necessary attributes that defined automatic role by attribute are defined by agenda "Automatic role by attribute".

After save identity (save from identity detail) it will be done recalculation for all automatic roles that has at least one rule with type IDENTITY, recalculation from identity is done for all contracts for saved identity. After save contract extended attributes (save from extended attribute detail) it will be done recalculation for all automatic roles that has at least one rule with type CONTRACT_EAV.

Automatically assigned roles have a significant safety impact. When creating, editing, or deleting, it is necessary that the process is approved. For this purpose, an agenda for requests for change of automatic roles has been created.

This request gets the approval process from the criticality defined for that role. Critical role determines what process the application must accomplish to implement it.

Processes of defined by the role criticality is defined here. Processes for approval change of an automatic role are different then processes using for approving assign role to one user. For clarity, both processes (role assignment, change of the automatic role) are defined in one final process.

Role can be duplicated by prepared bulk action. Bulk action is available on the roles table.

Action provides features:

• Select environment - role will be duplicated to selected environment. If the same as role's environment is selected or environment input is leaved empty, the role is duplicated on the same environment with suffix added into role's base code, e.g. roleOne ⇒ roleOne_1. If the different environment is selected, then duplicate with the same base code is created (or updated).
• Duplicate role attributes - creates (or updates) configured role attributes.
• Duplicate sub roles - creates (or updates) sub roles by business role definition (recursively). If the same environment is selected, the only role composition is created - exists sub role is used. If the different environment (~target environment) is used, then sub roles with the same environment as original are duplicated recursively into target environment.
• Duplicate automatic roles - creates (or updates) configured automatic roles. Both automatic roles by the tree structure and by the attribute are duplicated.

Read more about action implementation and how it's possible to extend it.

• Creating a role
• Defining permissions for a role
• Creating an automatically assigned role by organization structure
• Creating an automatically assigned role by identity attribute

• Authorization policies overview
• Permissions Setting Mechanism
• Automatic roles overview
• Automatic role request

• Authorization policies: base interfaces and classes
• Automatic roles by organization structure: heredity of roles
• Automatic roles by attribute, rules, and recalculation
• Duplicate role