To react quickly to special requests, you can assign the system entitlements directly to user accounts. You cannot directly assign system entitlements that have the Only use in IT Shop option set.
To assign user accounts directly to a system entitlement
-
In the Manager, select the Custom Target Systems > <target system> > System entitlements 1 category.
- OR -
In the Manager, select the Custom Target Systems > <target system> > System entitlements 2 category.
- OR -
In the Manager, select the Custom Target Systems > <target system> > System entitlements 3 category.
-
Select the system entitlement in the result list.
-
Select the Assign user accounts task.
-
In the Add assignments pane, assign the user accounts.
TIP: In the Remove assignments pane, you can remove assigned user accounts.
To remove an assignment
- Save the changes.
Related topics
To react quickly to special requests, you can assign groups directly to the user account. You cannot directly assign groups that have the Only use in IT Shop option set.
To assign groups directly to user accounts
-
In the Manager, select the Custom Target Systems > <target system> > User accounts category.
-
Select the user account in the result list.
-
Select the Assign groups and system entitlements task.
-
Select the Groups tab.
-
In the Add assignments pane, assign the groups.
TIP: In the Remove assignments pane, you can remove the assignment of groups.
To remove an assignment
- Save the changes.
Related topics
To react quickly to special requests, you can assign system entitlements directly to a user account. You cannot directly assign system entitlements that have the Only use in IT Shop option set.
To assign system entitlements directly to a user account
-
In the Manager, select the Custom Target Systems > <target system> > User accounts category.
-
Select the user account in the result list.
-
Select the Assign groups and system entitlements task.
-
Select the System entitlements 1 tab.
- OR -
Select the System entitlements 2 tab.
- OR -
Select the System entitlements 3 tab.
-
In the Add assignments pane, assign the system entitlements.
TIP: In the Remove assignments pane, you can remove system entitlement assignments.
To remove an assignment
- Save the changes.
Related topics
NOTE: The functionality described here for groups applies equally to system entitlements.
When groups are assigned to user accounts an identity 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 (UNSGroupBInUNSGroupB table).
The effectiveness of the assignments is mapped in the UNSAccountBInUNSGroupB/UNSAccountBHasUNSGroupB and BaseTreeHasUNSGroupB tables by the XIsInEffect column.
Example: The effect of group memberships
- Group A is defined with permissions for triggering requests in a target system. 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.
Jo User1 has a user account in this target system. They primarily belong to the "Marketing" department. The "Control group" business role and the "Finance" department are assigned to them 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 identity from being able to trigger a request and to pay invoices. That means, groups A, B, and C are mutually exclusive. An identity that checks invoices may not be able to make invoice payments as well. That means, groups B and C are mutually exclusive.
Table 13: Specifying excluded groups (UNSGroupBExclusion table)
|
Group A |
|
|
Group B |
Group A |
|
Group C |
Group B |
Table 14: Effective assignments
|
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. That means that the identity is authorized to trigger requests and to check invoices. If this should not be allowed, define further exclusion for group C.
Table 15: Excluded groups and effective assignments
|
Chris User2
|
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 no 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 belong to the same target system or the same target system type.
NOTE: Groups that are mutually exclusive, are determined within a target system type independently of the target system. The features must be taken into account in the definition of exclusion.
To exclude a group
-
In the Manager, select the Custom Target Systems > <target system> > 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 system entitlements
-
In the Manager, select the Custom Target Systems > <target system> > System entitlements 1 category.
- OR -
In the Manager, select the Custom Target Systems > <target system> > System entitlements 2 category.
- OR -
In the Manager, select the Custom Target Systems > <target system> > System entitlements 3 category.
-
Select a system entitlement in the result list.
-
Select the Exclude system entitlements 1 task, Exclude system entitlements 2 task, or Exclude system entitlements 3 task to match the selected system entitlement.
-
In the Add assignments pane, assign system entitlements that are mutually exclusive to the selected system entitlement.
- OR -
In the Remove assignments pane, remove the system entitlements that are no longer mutually exclusive.
- Save the changes.
.