Prerequisite
-
The user account must be labeled as a shared identity.
-
A pseudo employee must exist. The pseudo employee must be labeled as a shared identity and must have a manager.
-
The employees who are permitted to use the user account must be labeled as a primary identity.
To prepare an administrative user account for multiple employees
-
Label the user account as a shared identity.
-
In the Manager, select the Azure Active Directory > 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 a pseudo employee.
-
In the Manager, select the Azure Active Directory > User accounts category.
-
Select the user account in the result list.
-
Select the Change main data task.
-
On the General tab, select the pseudo employee from the Employee menu.
TIP: If you are the target system manager, you can choose 
to create a new pseudo employee.
-
Assign the employees who will use this administrative user account to the user account.
-
In the Manager, select the Azure Active Directory > User accounts category.
-
Select the user account in the result list.
-
Select the Assign employees authorized to use task.
-
In the Add assignments pane, add employees.
TIP: In the Remove assignments pane, you can remove assigned employees.
To remove an assignment
Related topics
Privileged user accounts are used to provide employees 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 the effect of temporarily or permanently disabling or deleting, or the security risk of an employee on its user accounts and group memberships for each 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 a person'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_Group, IsGroupAccount_SubSku, and IsGroupAccount_DeniedService columns 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 employees who work with privileged user accounts.
When the account definition is assigned to an employee, 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.
-
To use a prefix for the login name, in the Designer, set the TargetSystem | AzureAD | Accounts | PrivilegedAccount | AccountName_Prefix configuration parameter.
-
To use a postfix for the login name, in the Designer, set the TargetSystem | AzureAD | Accounts | PrivilegedAccount | AccountName_Postfix configuration parameter.
These configuration parameters are evaluated in the default installation, if a user account is marked with the Privileged user account property (IsPrivilegedAccount column). The user account login names are renamed according to the formatting rules. This also occurs if the user accounts are labeled as privileged using the Mark selected user accounts as privileged schedule. If necessary, modify the schedule in the Designer.
Related topics
In One Identity Manager, modifications to employee properties are forwarded to the associated user accounts and subsequently provisioned in the target system. In certain circumstances, it may be necessary to forward user account modifications in the target system to employee properties in One Identity Manager.
Example:
During testing, user accounts from the target system are only read into One Identity Manager and employees created. User account administration (creating, modifying, and deleting) should be done later through One Identity Manager. During testing, user accounts are modified further in the target system, which can lead to drifts in user account properties and employee properties. Due to this, user account modifications loaded on resynchronization should be temporarily published to employees who are already created. This means data is not lost when user account administration is put into effect through One Identity Manager.
To update employees when user accounts are modified
Modifications to user accounts are loaded into One Identity Manager during synchronization. These modifications are forwarded to the associated employees through subsequent scripting and processing.
User account properties are mapped to employee properties using the AAD_PersonUpdate_AADUser script. To make the mapping easier to customize, the script is overwritable.
To customize, create a copy of the script and start the script coding follows:
Public Overrides Function AAD_PersonUpdate_AADUser (ByVal UID_Account As String, oldUserPrincipalName As String, ProcID As String)
This redefines the script and overwrites the original. The process does not have to be changed in this case.
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 blocked. 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 AADUser table.
-
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 AADUser 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 detailed information on editing table definitions and configuring deferred deletion in the Designer, see the One Identity Manager Configuration Guide.
.