Different types of user accounts, such as default user accounts, administrative user accounts, service accounts, or privileged user accounts, can be mapped in One Identity Manager.

The following properties are used for mapping different user account types.

• Identity type

  The Identity type property (IdentityType column) is used to describe the type of user account.

  Table 19: Identity types of user accounts

  Identity type	Description	Value of the IdentityType column
  Primary identity	Identity's default user account.	Primary
  Organizational identity	Secondary user account used for different roles in the company, for example for subcontracts with other functional areas.	Organizational
  Personalized administrator identity	User account with administrative permissions, used by an identity.	Admin
  Sponsored identity	User account used for a specific purpose. For example, for training purposes.	Sponsored
  Shared identity	User account with administrative permissions, used by multiple identities.	Shared
  Service identity	Service account.	Service

• Privileged user account

  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).

Default user accounts

Normally, each identity obtains a default user account, which has the permissions they require for their regular work. The user accounts are linked to the identity. By default, the link between identity and SharePoint user account is set up through the authentication objects to which the user account is assigned. Alternatively, identities can also be directly linked to the user accounts. Such user accounts can be managed through account definitions. The effect of the link and the scope of the identity’s inherited properties on the user accounts can be configured through an account definition and its manage levels.

To create default user accounts through account definitions

1. Create an account definition and assign the Unmanaged and Full managed manage levels.

2. Specify how an identity's temporary deactivation, permanent deactivation, deletion, and security risks affect its user accounts and group memberships at each manage level.

3. Create a formatting rule for 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 setting are recommended for default user accounts:

   • In the mapping rules for the IsGroupAccount_SPSGroup and IsGroupAccount_SPSRLAsgn columns, use the default value 1 and set the Always use default value option.

   • In the mapping rule for the IdentityType column, use the default value Primary and enable Always use default value.

4. Enter the effective IT operating data for the target system. Select the concrete target system under Effects on.

   Specify in the departments, cost centers, locations, or business roles that IT operating data should apply when you set up a user account.

5. Assign the account definition to identities.

   When the account definition is assigned to an identity, a new user account is created through the inheritance mechanism and subsequent processing.

Administrative user accounts

An administrative user account must be used for certain administrative tasks. Administrative user accounts are usually predefined by the target system and have fixed names and login names, such as Administrator.

Administrative user accounts are imported into One Identity Manager during synchronization.

You can label administrative user accounts as a Personalized administrator identity or as a Shared identity. Proceed as follows to provide the identities who use this user account with the required permissions.

• Personalized admin identity

  1. Link the user account to a pseudo identity using the UID_Person column.

     Use an identity with the same identity type or create a new identity.

  2. Assign this identity to hierarchical roles.

• Shared identity

  1. Assign all identities with usage authorization to the user account.

  2. Link the user account to a pseudo identity using the UID_Person column.

     Use an identity with the same identity type or create a new identity.

  3. Assign this pseudo identity to hierarchical roles.

  The pseudo identity provides the user account with its permissions.

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).

To create privileged users through account definitions

1. Create an account definition. Create a new manage level for privileged user accounts and assign this manage level to the account definition.

2. 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.

3. Specify how an identity's temporary deactivation, permanent deactivation, deletion, and security risks affect its user accounts and group memberships in the manage level.

4. 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_SPSGroup and IsGroupAccount_SPSRLAsgn columns with a default value of 0 and set the Always use default value option.

5. 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.

6. 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.