NOTE: In order to easy understanding the behavior is described with respect to SAP groups in this section. It applies in the same way to roles and profiles.
Table 62: Configuration parameter for conditional inheritance
|
QER | Structures | Inherite | GroupExclusion |
Preprocessor relevant configuration parameter for controlling effectiveness of group memberships. If the configuration parameter is set, memberships can be reduced on the basis of exclusion definitions. Changes to this configuration 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.
The effectiveness of the assignments is mapped in the SAPUserInSAPGrp and BaseTreeHasSAPGrp tables by the XIsInEffect column.
Example: The effect of group memberships
- Group A is defined with permissions for triggering requests in a client. 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 client. 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 63: Specifying excluded groups (SAPGrpExclusion table)
|
Group A |
|
|
Group B |
Group A |
|
Group C |
Group B |
Table 64: 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. If this should not be allowed, define further exclusion for group C.
Table 65: Excluded groups and effective assignments
|
Jenny Basset
|
Marketing |
Group A |
|
Group C
|
|
Control group |
Group C |
Group B
Group A |
Prerequisites
-
The QER | Structures | Inherite | GroupExclusion configuration parameter is set.
In the Designer, set the configuration parameter and compile the database.
NOTE: If you disable the configuration parameter at a later date, model components and scripts that are not longer required, are disabled. SQL procedures and triggers are still carried out. For more information about the behavior of preprocessor relevant configuration parameters and conditional compiling, see the One Identity Manager Configuration Guide.
-
Mutually exclusive groups, roles, and profiles belong to the same client.
To exclude a group
-
In the Manager, select the SAP R/3 > 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 no longer mutually exclusive.
- Save the changes.
To exclude roles
-
In Manager, select the category SAP R/3 > Roles.
-
Select the role in the result list.
-
Select the Exclude SAP roles task.
- OR -
In the Remove assignments pane, remove the roles that are no longer mutually exclusive.
- Save the changes.
To exclude profiles
-
In the Manager, select the category SAP R/3 > Profiles.
-
Select a profile in the result list.
-
Select the Exclude roles task.
- OR -
In the Remove assignments pane, remove the profiles that are no longer mutually exclusive.
- Save the changes.
NOTE: In order to easy understanding the behavior is described with respect to SAP groups in this section. It applies in the same way to roles and profiles.
In One Identity Manager, user accounts can selectively inherit groups. To do this, groups and 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. Each table contains the category positions position 1 to position 63.
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 66: Category examples
| 1 |
Default user |
Default permissions |
| 2 |
System users |
System user permissions |
| 3 |
System administrator |
System administrator permissions |
Figure 5: Example of inheriting through categories.
To use inheritance through categories
-
Define the categories in the client.
NOTE: If central user administration is implemented, define the categories in the central system as well as in the child system. The same categories must be defined in the child system as in the central system so that groups from a child system can be inherited by user accounts.
-
Assign categories to user accounts through their main data.
-
Assign categories to groups, roles, and profiles through their main data.
Related topics
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
- Select the SAP R/3 > Groups category.
- Select the group in the result list.
- Select the Assign extended properties task.
- In the Add assignments pane, assign extended properties.
- OR -
In the Remove assignments pane, remove extended properties.
- Save the changes.
To specify extended properties for a role
- Select the SAP R/3 > Roles category.
- Select the role in the result list.
- Select the Assign extended properties task.
- Assign extended properties in Add assignments.
- OR -
Remove extended properties in Remove assignments .
- Save the changes.
To specify extended properties for a profile
- Select the SAP R/3 > Profiles category.
- Select a profile in the result list.
- Select the Assign extended properties task.
- Assign extended properties in Add assignments.
- OR -
Remove extended properties in Remove assignments .
- Save the changes.
You can view authorization objects and authorizations of One Identity Manager roles and profiles in SAP. All single profiles with their associated authorization objects and fields are displayed in a hierarchical overview.
To display role authorizations
- Select the SAP R/3 > Roles category.
- Select the role in the result list.
- Select the Show SAP authorizations task.
To display profile authorizations
- Select the SAP R/3 > Profiles category.
- Select a profile in the result list.
- Select the Show SAP authorizations task.
