After you have entered the main data, you can run the following tasks.
After you have entered the main data, you can run the following tasks.
To obtain an overview of a group
To obtain an overview of a profile
To obtain an overview of a role
Configuration parameter | Effect when set |
---|---|
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:
The effectiveness of the assignments is mapped in the
Jo User1 has a user account
By using suitable controls, you want to prevent an employee from
Effective group |
Excluded group |
---|---|
Group A |
|
Group B |
Group A |
Group C |
Group B |
Employee |
Member in role |
Effective group |
---|---|---|
Pat Identity1 |
Marketing |
Group A |
Jan User3 |
Marketing, finance |
Group B |
Jo User1 |
Marketing, finance, control group |
Group C |
Chris User2 |
Marketing, control group |
Group A, Group C |
Only the group C assignment is in effect for Jo User1. It is published in the target system. If Jo User1 leaves the "control group" business role at a later date, group B also takes effect.
The groups A and C are in effect for Chris User2 because the groups are not defined as mutually exclusive. If this should not be allowed, define further exclusion for group C.
Employee |
Member in role |
Assigned group |
Excluded group |
Effective group |
---|---|---|---|---|
Chris User2
|
Marketing |
Group A |
|
Group C
|
Control group |
Group C |
Group B
Group A |
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.
To exclude roles
In the Manager, select the SAP R/3 > Roles category.
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.
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.
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.
Category item | Categories for user accounts | Categories for groups |
---|---|---|
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
Assign categories to user accounts through their main data.
Assign categories to groups, roles, and profiles through their main data.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center