Memberships, such as user accounts in groups, are saved in assignment tables in the One Identity Manager database. During provisioning of modified memberships, changes made in the target system may be overwritten. This behavior can occur under the following conditions:
-
Memberships are saved in the target system as an object property in list form (Example: List of user accounts in the members~value property of a cloud group).
-
Memberships can be modified in either of the connected systems.
-
A provisioning workflow and provisioning processes are set up.
If one membership in One Identity Manager changes, by default, the complete list of members is transferred to the target system. Therefore, memberships that were previously added to the target system are removed in the process and 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
-
In the Manager, select the Universal Cloud Interface | Basic configuration data | Target system types category.
-
Select the Configure tables for publishing task.
-
Select the assignment tables that you want to set up for single provisioning. Multi-select is possible.
-
This option can only be enabled for assignment tables that have a base table with XDateSubItem or CCC_XDateSubItem column.
-
Assignment tables that are grouped together in a virtual schema property in the mapping must be marked identically.
-
Click Merge mode.
- Save the changes.
For each assignment table labeled like this, the changes made in 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 not the entire members list.
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.
You can restrict single provisioning of memberships with a condition. Once merge mode has been disabled for a table, the condition is deleted. Tables that have had the condition deleted or edited are marked with the following icon: 
. You can restore the original condition at any time.
To restore the default condition
-
Select the auxiliary table for which you want to restore the condition.
- Right-click on the selected row and select the Restore original values context menu item.
- Save the changes.
For more detailed information about provisioning memberships, see the One Identity Manager Target System Synchronization Reference Guide.
To smooth out spikes in data traffic, handling of processes for provisioning and single object synchronization can be distributed over several Job servers. This will also accelerate these processes.
NOTE: You should not implement load balancing for provisioning or single object synchronization on a permanent basis. Parallel processing of objects might result in dependencies not being resolved because referenced objects from another Job server have not been completely processed.
Once load balancing is no longer required, ensure that the synchronization server executes the provisioning processes and single object synchronization.
To configure load balancing
-
Configure the server and declare it as a Job server in One Identity Manager.
All Job servers must access the same cloud application as the synchronization server for the respective base object.
-
In the Synchronization Editor, assign a custom server function to the base object.
This server function is used to identify all the Job servers being used for load balancing.
If there is no custom server function for the base object, create a new one.
For more information about editing base objects, see the One Identity Manager Target System Synchronization Reference Guide.
-
In the Manager, assign this server function to all the Job servers that will be processing provisioning and single object synchronization for the base object.
Only select those Job servers that have the same configuration as the base object's synchronization server.
Once all the processes have been handled, the synchronization server takes over provisioning and single object synchronization again.
To use the synchronization server without load balancing.
- In the Synchronization Editor, remove the server function from the base object.
For detailed information about load balancing, see the One Identity Manager Target System Synchronization Reference Guide.
Detailed information about this topic
You can generate a report for analyzing problems that arise during synchronization, inadequate performance for example. The report contains information such as:
- Consistency check results
- Revision filter settings
- Scope applied
- Analysis of the data store
- Object access times in the One Identity Manager database and in the target system
To generate a synchronization analysis report
-
Open the synchronization project in the Synchronization Editor.
- Select the Help | Generate synchronization analysis report menu item and click Yes in the security prompt.
The report may take a few minutes to generate. It is displayed in a separate window.
- Print the report or save it in one of the available output formats.
Regular synchronization cannot be started until the synchronization project and the schedule are active.
To prevent regular synchronization
-
Open the synchronization project in the Synchronization Editor.
-
Select the start up configuration and deactivate the configured schedule.
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 synchronization project
-
Open the synchronization project in the Synchronization Editor.
-
Select the General view on the start page.
-
Click Deactivate project.
Detailed information about this topic
