Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
devel:documentation:roles [2017/11/03 23:01] poulm automatic roles chapter added |
devel:documentation:roles [2019/03/20 08:16] kotisovam [Role-differentiating icons] moved to admin guide |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | <- .: | ||
+ | |||
+ | {{tag> role incompatible business automatic SoD Segregation Duties }} | ||
+ | |||
+ | ====== Roles ====== | ||
+ | |||
+ | A role in CzechIdM is an entity representing a set (1 or many) of permissions/ | ||
+ | * **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, | ||
+ | |||
+ | From the perspective of the identity manager, it does not matter whether the user acquires an account in a specific application, | ||
+ | |||
+ | |||
+ | ===== Roles and contracts ===== | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | 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. | ||
+ | |||
+ | ===== Roles and environment ===== | ||
+ | |||
+ | 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), | ||
+ | * '' | ||
+ | * '' | ||
+ | * '' | ||
+ | |||
+ | ===== Role permissions===== | ||
+ | |||
+ | 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. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== Role criticality===== | ||
+ | The level of criticality can be set for every role. Criticality denotes, [[devel: | ||
+ | |||
+ | ===== Business roles ===== | ||
+ | Business roles (composition) can be defined on role detail. Business role could contain sub roles - all sub roles are assigned automatically, | ||
+ | Sub roles defined by business roles are recalculated on the background (by [[devel: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== Incompatible roles ===== | ||
+ | **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 [[https:// | ||
+ | |||
+ | When an incompatible role has been assigned to an identity, a **warning stating the incompatible role definition** is shown. | ||
+ | |||
+ | |||
+ | ==== Concurrence of incompatible roles and business roles ==== | ||
+ | |||
+ | 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, | ||
+ | |||
+ | |||
+ | {{ : | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | ===== Copying roles from a user ===== | ||
+ | |||
+ | Copying roles from a user is a new feature that allows one user to easily copy roles/ | ||
+ | |||
+ | This feature is available in the role request detail, see the new button in the picture: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | For more information about the feature with more detailed description, | ||
+ | |||
+ | ===== Automatically assigned roles by organization structure ===== | ||
+ | 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/ | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== Automatically assigned roles by attribute ===== | ||
+ | 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 " | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | 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. | ||
+ | |||
+ | ===== Requests for change automatically assigned roles ===== | ||
+ | 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 [[https:// | ||
+ | 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. | ||
+ | |||
+ | < | ||
+ | |||
+ | ===== Duplicating roles ===== | ||
+ | |||
+ | 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. | ||
+ | |||
+ | <note tip>When the role with the same base code already exist on the selected environment (environment has to be different), then new duplicate is not created, but the exists duplicate is updated.</ | ||
+ | |||
+ | Read [[.roles: | ||
+ | |||
+ | ===== Deduplicating roles ===== | ||
+ | |||
+ | Since roles are assigned to a contract not to an identity, it may well happen that an identity ends up having some role duplicities. Partly, it may be due to the fact that role definitions are changed over time, and from a certain point on they start to be assigned in a different way (say, automatically). And one and the same identity may meet the updated condition as well, hence it gets the same role all over again. | ||
+ | |||
+ | Deduplication is a bulk action that is available on User agenda. Deduplication allows removing only manually added roles that are duplicite with another automatic role or another manually added role. More on this feature in the admin guide and tutorial. | ||
+ | |||
+ | ====== Read more ====== | ||
+ | |||
+ | ===== Admin tutorials ===== | ||
+ | * [[tutorial: | ||
+ | * [[tutorial: | ||
+ | * [[tutorial: | ||
+ | * [[tutorial: | ||
+ | * [[tutorial: | ||
+ | * [[tutorial: | ||
+ | |||
+ | ===== Admin guide ===== | ||
+ | * [[.roles: | ||
+ | * [[.roles: | ||
+ | * [[.roles: | ||
+ | * [[.roles: | ||
+ | * [[.roles: | ||
+ | * [[.roles: | ||
+ | * [[.roles: | ||
+ | |||
+ | |||
+ | |||
+ | ===== Devel guide ===== | ||
+ | * [[.security: | ||
+ | * [[.identities: | ||
+ | * [[.roles: | ||
+ | * [[.roles: | ||