The main feature of One Identity Manager is to map employees together with the main data and permissions available to them in different target systems. To achieve this, information about user accounts and permissions can be read from the target system into the One Identity Manager database and linked to employees. This provides an overview of the permissions for each employee in all of the connected target systems. One Identity Manager offers the option of managing user accounts and their permissions. You can provision modifications in the target systems. Employees are supplied with the necessary permissions in the connected target systems according to their function in the company. Regular synchronization keeps data consistent between target systems and the One Identity Manager database.
Because requirements vary between companies, One Identity Manager offers different methods for supplying user accounts to employees. One Identity Manager supports the following methods for linking employees and their user accounts:
-
Employees can automatically obtain their account definitions using user account resources. If an employee does not yet have a user account in a client, a new user account is created. This is done by assigning account definitions to an employee using the integrated inheritance mechanism and subsequent process handling.
When you manage account definitions through user accounts, you can specify the way user accounts behave when employees are enabled or deleted.
- When user accounts are inserted, they can be automatically assigned to an existing employee or a new employee can be created if necessary. In the process, the employee main data is created on the basis of existing user account main data. This mechanism can be implemented if a new user account is created manually or by synchronization. However, this is not the One Identity Manager default method. You must define criteria for finding employees for automatic employee assignment.
- Employees and user accounts can be entered manually and assigned to each other.
Related topics
For more information about employee handling and administration, see the One Identity Manager Target System Base Module Administration Guide.
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
The Identity property (IdentityType column) is used to describe the type of user account.
Table 39: Identities of user accounts
|
Primary identity |
Employee's default user account. |
Primary |
|
Organizational identity |
Secondary user account used for different roles in the organization, for example for subcontracts with other functional areas. |
Organizational |
|
Personalized admin identity |
User account with administrative permissions, used by one employee. |
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 several employees. |
Shared |
|
Service identity |
Service account. |
Service |
NOTE: To enable working with identities for user accounts, the employees also need identities. You can only link user accounts to which an identity is assigned with employees who have this same identity.
The primary identity, the organizational identity, and the personalized admin identity are used for different user accounts, which can be used by the same actual employee to perform their different tasks within the company.
To provide user accounts with a personalized admin identity or an organizational identity for an employee, you create subidentities for the employee. These subidentities are then linked to user accounts, enabling you to assign the required permissions to the different user accounts.
User accounts with a sponsored identity, shared identity, or service identity are linked to pseudo employees that do not refer to a real employee. These pseudo employees are needed so that permissions can be inherited by the user accounts. When evaluating reports, attestations, or compliance checks, check whether pseudo employees need to be considered separately.
For more information about mapping employee identities, see the One Identity Manager Identity Management Base Module Administration Guide.
-
Privileged user account
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).
Default user accounts
Normally, each employee obtains a default user account, which has the permissions they require for their regular work. The user accounts are linked to the employee. The effect of the link and the scope of the employee’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
-
Create an account definition and assign the Unmanaged and Full managed manage levels.
-
Specify the effect of temporarily or permanently disabling, deleting, or the security risk of an employee on its user accounts and group memberships for each manage level.
-
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 a person'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_SAPGrp, IsGroupAccount_SAPProfile, and IsGroupAccount_SAPRole 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.
-
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.
-
Assign the account definition to employees.
When the account definition is assigned to an employee, 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.
NOTE: Some administrative user accounts can be automatically identified as privileged user accounts. To do this, in the Designer, enable the Mark selected user accounts as privileged schedule.
You can label administrative user accounts as a Personalized administrator identity or as a Shared identity. Proceed as follows to provide the employees who use this user account with the required permissions.
Privileged user accounts
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_SAPGrp, IsGroupAccount_SAPProfile, and IsGroupAccount_SAPRole 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.
If user accounts are managed through the central user administration () in SAP R/3, access to the child client can be guaranteed for or withdrawn from user accounts in One Identity Manager. To do this, clients are marked as central system or child system in One Identity Manager. User accounts are managed in the central system. You specify the client in which each user account obtains its access permissions. (SAPUserMandant table). Only SAP roles or profiles from this client can be assigned to a user account. A user account only has access authorizations in the central system if the central system is also explicitly assigned in the SAPUserMandant table.
NOTE: In One Identity Manager, only SAP groups from the central system are mapped. SAP groups are not administered through the central user administration.
To use automatic employee assignment for central user administration (CUA) user accounts, assign an account definition to the CUA central system using the SAPUser user table.
The access authorizations for central and child systems are read into theOne Identity Manager database through synchronization. In One Identity Manager, access authorization can be granted by IT Shop requests and indirect assignment, as well as by indirect assignment.
To grant a person access to a client by indirect assignment or request
-
Create an account definition to generate user accounts in the central system.
In the User account table field, select the SAPUser table. For more information, see Main data for an account definition.
This account definition is required to generate a user account in the central system if the employee does not yet have a user account.
-
Create an account definition for the client for which you want to grant access. The following special features apply:
Table 40: Main data of an account definition for accessing clients
| User account table |
Select SAPUserMandant from the menu. |
|
Target system |
Client for which you want to grant access. |
|
Required account definition |
From the menu, select the account definition to generate user accounts in the central system. A user account is then created in the central system if the employee does not yet have a user account. |
|
Manage level (initial) |
Select Unmanaged from the menu. |
|
Service item |
Service item through which you can request the account definition resource in the IT Shop. Assign an existing service item or add a new one. |
|
IT Shop |
Enable the option if access to the child system can be requested in the Web Portal. |
|
Only for use in IT Shop |
Enable the option if access to the child system can only be requested in the Web Portal. Indirect assignment by business roles or organizations is not possible. However, access by a user account to the child system can still be granted directly. |
An account definition is required for each child system and for the central system in which you want to grant access.
-
Assign the account definition for the client to a hierarchical role or IT Shop shelf.
-
Add the person as a member to the hierarchical role or as a customer to the IT Shop.
To grant a user account direct access to a client
You can now assign the SAP roles and profiles from this client to the user account.
Detailed information about this topic
Related topics
A user account can be linked to an employee in One Identity Manager. You can also manage user accounts separately from employees.
NOTE: It is recommended to use account definitions to set up user accounts for company employees. In this case, some of the main data described in the following is mapped through templates from employee main data.
NOTE: If employees are to obtain their user accounts through account definitions, the employees must own a central user account and obtain their IT operating data through assignment to a primary department, a primary location, or a primary cost center.If employees are to obtain their user accounts through account definitions, the employees must own a central SAP user account and obtain their IT operating data through assignment to a primary department, a primary location, or a primary cost center.
To create a user account
-
In the Manager, select the SAP R/3 > User accounts category.
-
Click 
in the result list.
-
On the main data form, edit the main data of the user account.
- Save the changes.
To edit main data of a user account
-
In the Manager, select the SAP R/3 > User accounts category.
-
Select the user account in the result list.
-
Select the Change main data task.
-
Edit the user account's resource data.
- Save the changes.
To manually assign a user account for an employee
-
In the Manager, select the Employees > Employees category.
-
Select the employee in the result list.
-
Select the Assign SAP user accounts task.
-
Assign a user account.
- Save the changes.
Detailed information about this topic
