Table 32: Configuration parameters for conditional inheritance
|
QER | Structures | Inherite | GroupExclusion |
Preprocessor relevant configuration parameter for controlling effectiveness of group memberships. If the parameter is set, memberships can be reduced on the basis of exclusion definitions. Changes to this parameter require the database to be recompiled. |
When groups are assigned to user accounts an employee may obtain two or more groups, which are not permitted in this combination. To prevent this, you can declare mutually exclusive groups. To do this, you specify which of the two groups should apply to the user accounts if both are assigned.
It is possible to assign an excluded group at any time either directly, indirectly, or with an IT Shop request. One Identity Manager determines whether the assignment is effective.
NOTE:
- You cannot define a pair of mutually exclusive groups. That means, the definition "Group A excludes group B" AND "Group B excludes groups A" is not permitted.
- You must declare each group to be excluded from a group separately. Exclusion definitions cannot be inherited.
- One Identity Manager does not check if membership of an excluded group is permitted in another group ( table).
The effectiveness of the assignments is mapped in the AADUserInGroup and AADBaseTreeHasGroup tables by the XIsInEffect column.
Example of the effect of group memberships
- Group A is defined with permissions for triggering requests in a tenant A group B is authorized to make payments. A group C is authorized to check invoices.
- Group A is assigned through the "Marketing" department, group B through "Finance", and group C through the "Control group" business role.
Clara Harris has a user account in this tenant. She primarily belongs to the "Marketing" department. The "Control group" business role and the "Finance" department are assigned to her secondarily. Without an exclusion definition, the user account obtains all the permissions of groups A, B, and C.
By using suitable controls, you want to prevent an employee from being able to trigger a request and to pay invoices. That means, groups A, B, and C are mutually exclusive. An employee that checks invoices may not be able to make invoice payments as well. That means, groups B and C are mutually exclusive.
Table 33: Specifying excluded groups (AADGroupExclusion table)
|
Group A |
|
|
Group B |
Group A |
|
Group C |
Group B |
Table 34: Effective assignments
|
Ben King |
Marketing |
Group A |
|
Jan Bloggs |
Marketing, finance |
Group B |
|
Clara Harris |
Marketing, finance, control group |
Group C |
|
Jenny Basset |
Marketing, control group |
Group A, Group C |
Only the group C assignment is in effect for Clara Harris. It is published in the target system. If Clara Harris leaves the "control group" business role at a later date, group B also takes effect.
The groups A and C are in effect for Jenny Basset because the groups are not defined as mutually exclusive. That means that the employee is authorized to trigger requests and to check invoices. If this should not be allowed, define further exclusion for group C.
Table 35: Excluded groups and effective assignments
|
Jenny Basset
|
Marketing |
Group A |
|
Group C
|
|
Control group |
Group C |
Group B
Group A |
Prerequisites
To exclude a group
-
In the Manager, select the Azure Active Directory | Groups category.
- Select a group in the result list.
-
Select the Exclude groups task.
-
In the Add assignments pane, assign the groups that are mutually exclusive to the selected group.
- OR -
In the Remove assignments pane, remove the groups that are not longer mutually exclusive.
- Save the changes.
In One Identity Manager, groups, administrator roles, subscriptions, and disabled services plans can be selectively inherited by user accounts. For this purpose, the groups (administrator roles, subscriptions, disabled service plans) and the user accounts are divided into categories. The categories can be freely selected and are specified using a mapping rule. Each category is given a specific position within the template. The mapping rule contains different tables. Use the user account table to specify categories for target system dependent user accounts. In the other tables enter your categories for the target system-dependent groups, administrator roles, subscriptions, and disabled service plans. Each table contains the Position 1 to Position 31 category positions.
Every user account can be assigned to one or more categories. Each group can also be assigned to one or more categories. The group is inherited by the user account when at least one user account category items matches an assigned group. The group is also inherited by the user account if the group or the user account is not put into categories.
NOTE: Inheritance through categories is only taken into account when groups are assigned indirectly through hierarchical roles. Categories are not taken into account when groups are directly assigned to user accounts.
Table 36: Category examples
| 1 |
Default user |
Default permissions |
| 2 |
System users |
System user permissions |
| 3 |
System administrator |
System administrator permissions |
Figure 2: Example of inheriting through categories.
To use inheritance through categories
- Define the categories in the tenant.
- Assign categories to user accounts through their master data.
- Assign categories to groups through their master data.
Related topics
A group owner can edit group properties.
To assign owners to a group
- Select the Azure Active Directory | Groups category.
- Select the group in the result list.
- Select the Assign owner task.
- Select the table containing the owner from the Table menu at the top of the form. You have the following option:
- Azure Active Directory user accounts
-
In the Add assignments pane, assign owners.
- OR -
In the Remove assignments pane, remove owners.
- Save the changes.
Extended properties are meta objects, such as operating codes, cost codes, or cost accounting areas that cannot be mapped directly in One Identity Manager.
To specify extended properties for a group
-
In the Manager, select the Azure Active Directory | Groups category.
-
Select the group in the result list.
-
Select the Assign extended properties task.
-
In the Add assignments pane, assign extended properties.
TIP: In the Remove assignments pane, you can remove assigned extended properties.
To remove an assignment
- Select the extended property and double-click
.
- Save the changes.
For more detailed information about setting up extended properties, see the One Identity Manager Identity Management Base Module Administration Guide.
