Updating schemas
All the schema data (schema types and schema properties) of the target system schema and the One Identity Manager schema are available when you are editing a synchronization project. Only a part of this data is really needed for configuring synchronization. If a synchronization project is finished, the schema is compressed to remove unnecessary data from the synchronization project. This can speed up the loading of the synchronization project. Deleted schema data can be added to the synchronization configuration again at a later point.
If the target system schema or the One Identity Manager schema has changed, these changes must also be added to the synchronization configuration. Then the changes can be added to the schema property mapping.
To include schema data that have been deleted through compression and schema modifications in the synchronization project, update each schema in the synchronization project. This may be necessary if:
To update a system connection schema
-
Open the synchronization project in the Synchronization Editor.
-
Select the Configuration | Target system category.
- OR -
Select the Configuration | One Identity Manager connection category.
-
Select the General view and click Update schema.
- Confirm the security prompt with Yes.
This reloads the schema data.
To edit a mapping
-
Open the synchronization project in the Synchronization Editor.
-
Select the Mappings category.
-
Select a mapping in the navigation view.
Opens the Mapping Editor. For more detailed information about mappings, see the One Identity Manager Target System Synchronization Reference Guide.
NOTE: The synchronization is deactivated if the schema of an activated synchronization project is updated. Reactivate the synchronization project to synchronize.
Post-processing outstanding objects
Objects, which do not exist in the target system, can be marked as outstanding in One Identity Manager by synchronizing. This prevents objects being deleted because of an incorrect data situation or an incorrect synchronization configuration.
Outstanding objects:
-
Cannot be edited in One Identity Manager.
-
Are ignored by subsequent synchronizations.
-
Are ignored by inheritance calculations.
This means, all memberships and assignments remain intact until the outstanding objects have been processed.
Start target system synchronization to do this.
To post-process outstanding objects
-
In the Manager, select the Azure Active Directory | Target system synchronization: Azure Active Directory category.
All the synchronization tables assigned to the Azure Active Directory target system type are displayed in the navigation view.
-
On the Target system synchronization form, in the Table / object column, open the node of the table for which you want to post-process outstanding objects.
All objects that are marked as outstanding are shown. The Last log entry and Last method run columns display the time at which the last entry was made in the synchronization log and which processing method was executed. The No log available entry can mean the following:
-
The synchronization log has already been deleted.
- OR -
-
An assignment from a member list has been deleted from the target system.
The base object of the assignment was updated during the synchronization. A corresponding entry appears in the synchronization log. The entry in the assignment table is marked as outstanding, but there is no entry in the synchronization log.
-
An object that contains a member list has been deleted from the target system.
During synchronization, the object and all corresponding entries in the assignment tables are marked as outstanding. However, an entry in the synchronization log appears only for the deleted object.
TIP:
To display object properties of an outstanding object
- Select the object on the target system synchronization form.
- Open the context menu and click Show object.
-
Select the objects you want to rework. Multi-select is possible.
-
Click on one of the following icons in the form toolbar to execute the respective method.
Table 6: Methods for handling outstanding objects
|
|
Delete |
The object is immediately deleted from the One Identity Manager database. Deferred deletion is not taken into account. The Outstanding label is removed from the object.
Indirect memberships cannot be deleted. |
|
|
Publish |
The object is added to the target system. The Outstanding label is removed from the object.
The method triggers the HandleOutstanding event. This runs a target system specific process that triggers the provisioning process for the object.
Prerequisites:
|
|
|
Reset |
The Outstanding label is removed for the object. |
- Confirm the security prompt with Yes.
NOTE: By default, the selected objects are processed in parallel, which speeds up execution of the selected method. If an error occurs during processing, the action is stopped and all changes are discarded.
Bulk processing of objects must be disabled if errors are to be localized, which means the objects are processed sequentially. Failed objects are named in the error message. All changes that were made up until the error occurred are saved.
To disable bulk processing
You must customize your target system synchronization to synchronize custom tables.
To add custom tables to target system synchronization
-
In the Manager, select the Azure Active Directory | Basic configuration data | Target system types category.
-
In the result list, select the Azure Active Directory target system type.
-
Select the Assign synchronization tables task.
-
In the Add assignments pane, assign custom tables to the outstanding objects you want to handle.
- Save the changes.
-
Select the Configure tables for publishing task.
-
Select the custom tables that contain the outstanding objects that can be published in the target system and set the Publishable option.
- Save the changes.
NOTE: The target system connector must have write access to the target system in order to publish outstanding objects that are being post-processed. That means, the Connection is read-only option must not be set for the target system connection.
Configuring the provisioning of memberships
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 property of an Azure Active Directory 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 Azure Active Directory | Basic configuration data | Target system types category.
-
Select Azure Active Directory in the result list.
-
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 (for example, AADUserInGroup and AADGroupInGroup).
-
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.
Accelerating provisioning and single object synchronization
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 Azure Active Directory tenant 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
to disable bulk processing.