Memberships, for example, user accounts in
If a membership in One Identity Manager changes, the complete list of members is transferred to the target system by default. Memberships, previously added to the target system are removed by this; previously deleted memberships are added again.
To prevent this, provisioning can be configured such that only the modified membership is provisioned in the target system. The corresponding behavior is configured separately for each assignment table.
To allow separate provisioning of memberships
For each assignment table labeled like this, the changes made in the One Identity Manager are saved in a separate table. During modification provisioning, the members list in the target system is compared to the entries in this table. This means that only modified memberships are provisioned and the members list does not get entirely overwritten.
|
NOTE: The complete members list is updated by synchronization. During this process, objects with changes but incomplete provisioning are not handled. These objects are logged in the synchronization log. |
For more detailed information about provisioning memberships, see the One Identity Manager Target SystemAn instance of a target system in which the employees managed by One Identity Manager have access to network resources. Example: An Active Directory domain X for target system type "Active Directory", a directory Y for target system type "LDAP", a client Z for target system type "SAP R/3". Synchronization
The process of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. Reference Guide.
|
NOTE: Changes to user account memberships in single role are always provisioned individually. Therefore, single provisioning cannot be configured for the table SAPUserInSAPRole. |
You can generate a report for analyzing problems which occur during synchronization, for example, insufficient performance. The report contains information such as:
To generate a synchronization analysis report
Open the synchronization project in the Synchronization EditorOne Identity Manager tool for configuring target system synchronization..
The report may take a few minutes to generate. It is displayed in a separate window.
Regular synchronization cannot be started until the synchronization project and the schedule are active.
To prevent regular synchronization
Now you can only start synchronization manually.
An activated synchronization project can only be edited to a limited extend. The schema in the synchronization project must be updated if schema modifications are required. The synchronization project is deactivated in this case and can be edited again.
Furthermore, the synchronization project must be deactivated if synchronization should not be started by any means (not even manually).
To deactivate the loaded synchronization project
To manage an SAP R/3 environment in One Identity Manager, the following data is relevant.
Use configuration parameters to configure the behavior of the system's basic settings. One Identity Manager provides default settings for different configuration parameters. Check the configuration parameters and modify them as necessary to suit your requirements.
Configuration parameters are defined in the One Identity Manager modules. Each One Identity Manager module can also install configuration parameters. You can find an overview of all configuration parameters in the category Base data | General | Configuration parameters in the Designer.
For more information, see Appendix: Configuration Parameters for Managing SAP R/3.
One Identity Manager has account definitions for automatically allocating user accounts to employees during working hours. You can create account definitions for every target system. If an employee does not have a user account in the target system, a new user account is created. This is done by assigning account definitions to an employee using the integrated inheritance mechanism followed by process handling.
provides you with support for creating complex password policies, for example, for system user passwords, the employees' central password as well as passwords for individual target systems. Password polices apply not only when the user enters a password but also when random passwords are generated.
Predefined password policies are supplied with the default installation that you can user or customize if required. You can also define your own password policies.
You have the different options for issuing an initial password for user accounts. The central password of the assigned employee can be aligned with the user account password, a predefined, fixed password can be used or a randomly generated initial password can be issued.
For more information, see Initial Password for New SAP User Accounts.
When a new user account is created, the login data are send to a specified recipient. In this case, two messages are sent with the user name and the initial password. Mail templates are used to generate the messages.
For more information, see Email Notifications about Login Data.
User accounts can be assigned a default login language. Login languages can be loaded into the One Identity Manager database through synchronization.
Target system types are required for configuring target system comparisons. Tables containing outstanding objects are maintained on target system types.
For more information, see Post-Processing Outstanding Objects.
In order to handle SAP R/3 specific processes in One Identity Manager, the synchronization server and its server functionality must be declared.
A default application role exists for the target system manager in the One Identity Manager. Assign this application to employees who are authorized to edit the
Define other application roles, if you want to limit target system managers' access permissions to individual
© 2023 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy