You can use deferred deletion to specify how long the user accounts remain in the database after deletion is triggered before they are finally removed. By default, user accounts are finally deleted from the database after 30 days. First, the user accounts are disabled or locked. You can reenable the user accounts up until deferred deletion runs. After deferred deletion is run, the user accounts are deleted from the database and cannot be restored anymore.
You have the following options for configuring deferred deletion.
-
Global deferred deletion: Deferred deletion applies to user accounts in all target system. The default value is 30 days.
In the Designer, enter a different value for deferred deletion in the Deferred deletion [days] property of the UNSAccountB table.
-
Target system specific deferred deletion: Deferred deletion can be configured individually for each target system. This deferred deletion overrides global deferred deletion.
To enable deferred deletion separately for each target system
-
In the Manager, configure deferred deletion for the target system.
-
In the Manager, select the Custom Target Systems > Basic configuration data > Target systems category.
-
In the result list, select a target system and run the Change main data task.
-
On the General tab, under Deferred deletion [days], enter the deferred deletion value in days.
- Save the changes.
-
In the Designer, create a Script (deferred deletion) in the UNSAccountB table.
Example: Script for target system-specific deferred deletion
Deferred deletion of user accounts in a custom target system depends on the deferred deletion of the target system (UNSRootB.DeleteDelayDays). The following script is given in the UNSAccountB table.
If $FK(UID_UNSRootB).DeleteDelayDays:Int$ > 0 Then
Value = $FK(UID_UNSRootB).DeleteDelayDays:Int$
End If
-
Object-specific deferred deletion: Deferred deletion can be configured depending on certain properties of the accounts.
To use object-specific deferred deletion, in the Designer, create a Script (deferred deletion) for the UNSAccountB table.
Example: Script for object-specific deferred deletion
Deferred deletion of privileged user accounts is 10 days. The following Script (deferred deletion) is entered in the table.
If Not $IsPrivilegedAccount:Bool$ Then
End If
For more information on editing table definitions and configuring deferred deletion in the Designer, see the One Identity Manager Configuration Guide.
Groups and system entitlements represent the objects used in the target system to control access to target system resources. A user account obtains the required permissions for accessing target system resources through its memberships in groups and system entitlements.
In One Identity Manager, you can assign groups and system entitlements directly to user accounts or they can be inherited through departments, cost centers, locations, or business roles. Users can also request the groups and system entitlements through the Web Portal. To do this, groups and system entitlements are provided in the IT Shop.
Detailed information about this topic
Many target systems use more than one group type to map entitlements. For example, these might be groups, roles, or entitlement sets. There are four different types mapped in One Identity Manager
Table 10: Types of system entitlements used
|
Groups |
UNSGroupB |
|
System entitlements 1 |
UNSGroupB1 |
|
System entitlements 2 |
UNSGroupB2 |
|
System entitlements 3 |
UNSGroupB3 |
You decide when you set up synchronization, which types are mapped in which tables.
A user account obtains the required entitlements for accessing target system resources through its assignments to groups or system entitlements. Depending on the target system, assignments are maintained either on user accounts (user-based assignment) or on groups or system entitlements (entitlement-based assignment). In One Identity Manager, you can configure the behavior accordingly. Memberships are stored in the following tables:
Table 11: User-based assignment
|
UNSAccountBHasUNSGroupB |
Groups: Assignments to user accounts |
|
UNSAccountBHasUNSGroupB1 |
System entitlements 1: Assignments to user accounts |
|
UNSAccountBHasUNSGroupB2 |
System entitlements 2: Assignments to user accounts |
|
UNSAccountBHasUNSGroupB3 |
System entitlements 3: Assignments to user accounts |
Table 12: Entitlement-based assignment
|
UNSAccountBInUNSGroupB |
User accounts: Assignment to groups |
|
UNSAccountBInUNSGroupB1 |
User accounts: Assignment to system entitlements 1 |
|
UNSAccountBInUNSGroupB2 |
User accounts: Assignment to system entitlements 2 |
|
UNSAccountBInUNSGroupB3 |
User accounts: Assignment to system entitlements 3 |
To specify which types of system entitlements to use
-
In the Manager, select the Custom Target Systems > Basic configuration data > Target systems category.
-
In the result list, select a target system and run the Change main data task.
-
In the System entitlement types used drop-down, select all the types to use in the connected target system.
-
In the User account has memberships drop-down, select all the types with saved user account assignments.
-
Enable the system entitlements with saved user account assignments.
-
Disable the system entitlements with saved system entitlements assignments.
- Save the changes.
Example
In a target system, entitlements are managed as groups and profiles. Assignments to groups are maintained on the group objects, assignments to profiles on the user accounts. In the One Identity Manager, groups are mapped in the UNSGroupsB table, profiles in the UNSGroupB1 table.
-
In the Types of system entitlements used drop-down, set the Group and System entitlement 1 values.
-
In the User account has memberships drop-down, only set the System entitlement 1 value.
This saves the assignments to system entitlement in the UNSAccountBHasUNSGroupB1, and UNSAccountBInUNSGroupB tables.
NOTE: When setting up attestation procedures, compliance rules, or company policies using system entitlements, be sure to select the correct assignment tables to look at both user-based and entitlement-based assignments.
To set up functions independently of the target system configurations, use the target system mapping in the Unified Namespace. Both user-based and entitlement-based assignments for all types of system entitlements are mapped in the UNSAccountInUNSGroup table; the UNSGroup table contains all system entitlements regardless of type.
For more information about the Unified Namespace, see the One Identity Manager Target System Base Module Administration Guide.
Detailed information about the attestation functions, compliance rules, and company policies can be found in the following guides:
One Identity Manager Attestation Administration Guide
One Identity Manager Compliance Rules Administration Guide
One Identity Manager Company Policies Administration Guide
Groups and system entitlements can be assigned directly or indirectly to a user account. Indirect assignment is carried out by sorting the identity, and the groups and system entitlements into hierarchical roles, such as departments, cost centers, locations, or business roles. If the identity has a user account in the target system, the groups and system entitlements in the role are inherited by this user account. You can assign groups and system entitlements to user accounts that belong to the same target system or to different target systems with the same target system type. For more information, see Target system types for custom target systems.
Groups and system entitlements can also be requested in the Web Portal. To do this, add identities to a shop as customers. All groups and system entitlements assigned to this shop as products can be requested by the customers. After approval is granted, requested groups and system entitlements are assigned to the identities.
Through system roles, groups and system entitlements can be grouped together and assigned to identities and workdesks as a package. You can create system roles that contain only groups or system entitlements. You can also group any number of company resources into a system role.
To react quickly to special requests, you can assign groups and system entitlements directly to user accounts.
|
Basic principles for assigning and inheriting company resources |
One Identity Manager Identity Management Base Module Administration Guide
One Identity Manager Business Roles Administration Guide |
|
Assigning company resources through IT Shop requests |
One Identity Manager IT Shop Administration Guide |
|
System roles |
One Identity Manager System Roles Administration Guide |
Detailed information about this topic
