NOTE: The Manager is locked for editing throughout. To edit objects in the Manager, close the Synchronization Editor.
To open an existing synchronization project in the Synchronization Editor
You can manage SAP R/3 user accounts with One Identity Manager. One Identity Manager concentrates on setting up and editing SAP user accounts. Groups, roles, and profiles are mapped in SAP, in order to provide the necessary permissions for One Identity Manager user accounts. The necessary data for system measurement is also mapped. The system measurement data is available in One Identity Manager, but the measurement itself takes place in the SAP R/3 environment.
If user accounts are managed through the central user administration (CUA
NOTE: The following user accounts are read into the One Identity Manager database during synchronization, but cannot be edited, created, or deleted in One Identity Manager.
sap*
sapcpic
sapjsf
ddic
j2ee_admin
j2ee_guest
sladpiuser
slddsuser
adsuser
ads_agent
tmsadm
earlywatch
Changes to these user accounts can only be made in SAP R/3 and transferred to the One Identity Manager by subsequent synchronization.
The main feature of One Identity Manager is to map identities 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 identities. This provides an overview of the permissions for each identity 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. Identities 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 identities. One Identity Manager supports the following methods for linking identities and their user accounts:
Identities can automatically obtain their account definitions using user account resources.
If an identity 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 identity using the integrated inheritance mechanisms and subsequent process handling.
When you manage account definitions through user accounts, you can specify the way user accounts behave when identities are enabled or deleted.
When user accounts are inserted, they can be automatically assigned to an existing identity
Identities and user accounts can be entered manually and assigned to each other.
For more information about basic handling and administration of identities and user accounts, 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 type
The Identity type property (IdentityType column) is used to describe the type of user account.
| 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).
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. 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
Create an account definition and assign the Unmanaged and Full managed manage levels.
Specify how an identity's temporary deactivation, permanent deactivation, deletion, and security risks affect its user accounts and group memberships at 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 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_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 identities.
When the account definition is assigned to an identity, a new user account is created through the inheritance mechanism and subsequent processing.
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 identities who use this user account with the required permissions.
Personalized admin identity
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.
Assign this identity to hierarchical roles.
Shared identity
Assign all identities with usage authorization to the user account.
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.
Assign this pseudo identity to hierarchical roles.
The pseudo identity provides the user account with its permissions.
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_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 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:
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
