Editing search criteria for automatic identity assignment
NOTE: One Identity Manager supplies a default mapping for identity assignment. Only carry out the following steps when you want to customize the default mapping.
The criteria for identity assignments are defined for the client. You specify which user account properties must match the identity’s properties such that the identity can be assigned to the user account. You can limit search criteria further by using format definitions.
The search criterion is written in XML notation to the Search criteria for automatic identity assignment column (AccountToPersonMatchingRule) in the SAPMandant table.
Search criteria are evaluated when identities are automatically assigned to user accounts. Furthermore, you can create a suggestion list for assignments of identities to user accounts based on the search criteria and make the assignment directly.
NOTE: Object definitions for user accounts that can have search criteria applied to them are predefined. For example, if you require other objects definitions that limit a preselection of user accounts, set up the respective custom object definitions in the Designer. For more information, see the One Identity Manager Configuration Guide.
To specify criteria for identity assignment
- Select the SAP R/3 > Clients category.
- Select the client in the result list.
- Select the Define search criteria for identity assignment task.
- Specify which user account properties must match with which identity so that the identity is linked to the user account.
Table 51: Standard search criteria for user accounts
| SAP user accounts of the type "Dialog" |
Central SAP user account (CentralSAPAccount) |
User account (Accnt) |
- Save the changes.
Direct assignment of identities to user accounts based on a suggestion list
In the Assignments pane, you can create a suggestion list for assignments of identities to user accounts based on the search criteria and make the assignment directly. User accounts are grouped in different views for this.
Table 52: Manual assignment view
|
Suggested assignments |
This view lists all user accounts to which One Identity Manager can assign an identity. All identities are shown that were found using the search criteria and can be assigned. |
|
Assigned user accounts |
This view lists all user accounts to which an identity is assigned. |
|
No identity assignment |
This view lists all user accounts to which no identity is assigned and for which no identity was found using the search criteria. |
TIP: By double-clicking on an entry in the view, you can view the user account and identity main data.
To apply search criteria to user accounts
To assign identities directly using a suggestion list
- Click Suggested assignments.
- Click Selection on all user accounts to which you want to assign the suggested identities. Multi-select is possible.
- Click Assign selected.
- Confirm the security prompt with Yes.
The identities found using the search criteria are assigned to the selected user accounts.
– OR –
- Click No identity assignment.
- Click Select identity for the user account to which you want to assign an identity. Select an identity from the menu.
- Click Selection on all the user accounts to which you want to assign the selected identities. Multi-select is possible.
- Click Assign selected.
- Confirm the security prompt with Yes.
The identities displayed in the Identity column are assigned to the selected user accounts
.
To remove assignments
- Click Assigned user accounts.
- Click Selection on all user accounts you want to delete the identity assignment from. Multi-select is possible.
- Click Remove selected.
- Confirm the security prompt with Yes.
The assigned identities are removed from the selected user accounts.
For more information about defining search criteria, see the One Identity Manager Target System Base Module Administration Guide.
Related topics
Automatically creating departments based on SAP user account information
You can create new departments in One Identity Manager based on user accounts’ department data. In addition, you can specify that departments of user account’s identities are classified as the primary department. These identities can obtain their company resources through these assignments if One Identity Manager is configured correspondingly.
Prerequisites for using this method
- Identities must be created automatically when user accounts are added or modified. At least one of the following configuration parameters must be activated and the corresponding method implemented.
Table 53: Configuration Parameter for automatic identity assignment
|
TargetSystem | SAPR3 | PersonAutoDefault |
Based on the given mode, identities that were added to the database outside the synchronization are automatically assigned to user accounts. |
|
TargetSystem | SAPR3 | PersonAutoFullsync |
Based on the given mode, identities that were added to or updated in the database by synchronization are automatically assigned to user accounts. |
-
There is no synchronization project set up for personnel planning data.
During synchronization of personnel planning data, departments that have been created already from SAP user account data are marked as outstanding. Use this method to automatically create departments from user account data only when departments are not added by synchronizing personnel planning data. For more information about synchronizing personnel planning data, see the One Identity Manager Administration Guide for SAP R/3 Structural Profiles Add-on.
To create departments from user account data
-
In the Designer, enable the TargetSystem | SAPR3 | AutoCreateDepartment configuration parameter.
For all departments imported into the One Identity Manager database in this way, SAP R/3 is given as the data source for the import (column ImportSource='SAP').
Related topics
Locking SAP user accounts
The way you lock user accounts depends on how they are managed.
Scenario: The user accounts are linked to identities and are managed through account definitions.
User accounts managed through account definitions are locked when the identity is temporarily or permanently disabled. The behavior depends on the user account manage level. Accounts with the Full managed manage level are disabled depending on the account definition settings. The Lock user account and Unlock user account tasks cannot be applied to these accounts. For user accounts with a manage level, configure the required behavior using the template in the SAPUser.U_Flag column.
Scenario: The user accounts are linked to identities. No account definition is applied.
User accounts managed through user account definitions are locked when the identity is temporarily or permanently disabled. The behavior depends on the QER | Person | TemporaryDeactivation configuration parameter
-
If the configuration parameter is set, the identity’s user accounts are locked when the identity is permanently or temporarily disabled. The Lock user account and Unlock user account tasks cannot be applied to these accounts.
-
If the configuration parameter is not set, the identity’s properties do not have any effect on the associated user accounts.
To lock the user account when the configuration parameter is disabled
-
In the Manager, select the SAP R/3 > User accounts category.
-
Select the user account in the result list.
-
Select the Lock user account task.
-
Confirm the prompt with OK.
Scenario: The user accounts are not linked to identities.
To lock a user account that is no longer linked to an identity
-
In the Manager, select the SAP R/3 > User accounts category.
-
Select the user account in the result list.
-
Select the Lock user account task.
-
Confirm the prompt with OK.
A process is generated, which publishes this user account modification in the target system. Once the lock has been published in the target system, the User account locked option is enabled on the Login data tab. The user can no longer log in with this user account.
To unlock a user account
- Select the SAP R/3 > User accounts category.
- Select the user account in the result list.
- Select the Unlock user account task.
- Confirm the prompt with OK.
This generates a process that publishes the change in the target system. The User account locked option is disabled as soon as the process is successfully completed.
Detailed information about this topic
For more information, see theOne Identity Manager Target System Base Module Administration Guide.
Related topics
Deleting and restoring SAP user accounts
NOTE: As long as an account definition for an identity is valid, the identity retains the user account that was created by it. If the account definition assignment is removed, the user account that was created from this account definition, is deleted. User accounts marked as Outstanding are only deleted if the QER | Person | User | DeleteOptions | DeleteOutstanding configuration parameter is set.
To delete a user account
- Select the SAP R/3 > User accounts category.
- Select the user account in the result list.
- Click
to delete the user account.
- Confirm the security prompt with Yes.
To restore a user account
- Select the SAP R/3 > User accounts category.
- Select the user account in the result list.
- Click
in the result list.
Configuring deferred deletion
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.Deferred deletion has no influence over the login permission in assigned child systems.
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 SAPUser 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 SAPUser 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.
