To remove a group from all IT Shop shelves
-
In the Manager, select the Unix > Groups (non role-based login) category.
- OR -
In the Manager, select the Entitlements > Unix groups (role-based login) category.
-
Select the group in the result list.
-
Select the Remove from all shelves (IT Shop) task.
- Confirm the security prompt with Yes.
-
Click OK.
The group is removed from all shelves by the One Identity Manager Service. All requests and assignment requests with this group are canceled in the process.
Related topics
Groups can be assigned directly or indirectly to user accounts. Indirect assignment is done by allocating the employee and groups into company structures such as departments, cost centers, locations, or business roles. If the employee has a user account in a Unix-based target system, the groups in the role are inherited by this user account.
To react quickly to special requests, you can assign groups directly to user accounts. You cannot directly assign groups that have the Only use in IT Shop option.
To assign user accounts directly to a group
-
In the Manager, select the Unix > Groups category.
-
Select the group 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
Groups can be assigned directly or indirectly to a user account. Indirect assignment is carried out by allocating the employee and groups in hierarchical roles, such as departments, cost centers, locations, or business roles. If the employee has a user account in Unix, the groups in the role are inherited by this user account.
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.
To assign groups directly to user accounts
-
In the Manager, select the Unix > User accounts category.
-
Select the user account in the result list.
-
Select the Assign groups task.
-
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
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 UNXAccountInUNXGroup and BaseTreeHasUNXGroup tables by the XIsInEffect column.
Example: The effect of group memberships
- Group A is defined with permissions for triggering requests in a host. 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 host. 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 12: Specifying excluded groups (UNXGroupExclusion table)
|
Group A |
|
|
Group B |
Group A |
|
Group C |
Group B |
Table 13: 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 14: 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 belong to the same host.
To exclude a group
-
In the Manager, select the Unix > 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.
.