Providing administrative user accounts for several people
Use this task to create an administrative user account that can be used by more that one identity.
Prerequisite
-
The user account must be labeled as a shared identity.
-
There must be an identity with the type Shared identity available. The shared identity must have a manager.
-
The identities who are permitted to use the user account must be labeled as a primary identity.
To prepare an administrative user account for multiple identities
-
Label the user account as a shared identity.
-
In the Manager, select the Custom Target Systems > <target system> > User accounts category.
-
Select the user account in the result list.
-
Select the Change main data task.
-
On the General tab, in the Identity menu, select Shared identity.
-
Link the user account to an identity.
-
In the Manager, select the Custom Target Systems > <target system> > User accounts category.
-
Select the user account in the result list.
-
Select the Change main data task.
-
On the General tab, in the Identity menu, select an identity the type Shared identity.
TIP: If you are the target system manager, you can use the 
button to create a new shared identity.
-
Assign the identities who will use this administrative user account to the 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 identities authorized to use task.
-
In the Add assignments pane, add identities.
TIP: In the Remove assignments pane, you can remove assigned identities.
To remove an assignment
Related topics
Privileged user accounts
Privileged user accounts are used to provide identities with additional privileges. This includes administrative user accounts or service accounts, for example. The user accounts are labeled with the Privileged user account property (IsPrivilegedAccount column).
NOTE: The criteria according to which user accounts are automatically identified as privileged are defined as extensions to the view definition (ViewAddOn) in the TSBVAccountIsPrivDetectRule table (which is a table of the Union type). The evaluation is done in the TSB_SetIsPrivilegedAccount script.
To create privileged users through account definitions
-
Create an account definition. Create a new manage level for privileged user accounts and assign this manage level to the account definition.
-
If you want to prevent the properties for privileged user accounts from being overwritten, set the IT operating data overwrites property for the manage level to Only initially. In this case, the properties are populated just once when the user accounts are created.
-
Specify how an identity's temporary deactivation, permanent deactivation, deletion, and security risks affect its user accounts and group memberships in the manage level.
-
Create a formatting rule for the IT operating data.
You use the mapping rule to define which rules are used to map IT operating data for user accounts and which default values are used if no IT operating data can be determined through an identity's primary roles.
The type of IT operating data required depends on the target system. The following settings are recommended for privileged user accounts:
-
In the mapping rule for the IsPrivilegedAccount column, use the default value 1 and set the Always use default value option.
-
You can also specify a mapping rule for the IdentityType column. The column owns different permitted values that represent user accounts.
-
To prevent privileged user accounts from inheriting the entitlements of the default user, define a mapping rule for the IsGroupAccount column with a default value of 0 and set the Always use default value option.
-
Enter the effective IT operating data for the target system.
Specify in the departments, cost centers, locations, or business roles which IT operating data should apply when you set up a user account.
-
Assign the account definition directly to identities who work with privileged user accounts.
When the account definition is assigned to an identity, a new user account is created through the inheritance mechanism and subsequent processing.
TIP: If customization requires that the login names of privileged user accounts follow a defined naming convention, specify how the login names are formatted in the template.
Related topics
Setting deferred deletion for custom target system user accounts
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:
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:
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.
Related topics
Managing assignments of groups and system entitlements
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
.