Chat now with support
Chat with Support

Identity Manager 8.1.4 - Target System Synchronization Reference Guide

Target system synchronization with the Synchronization Editor Working with the Synchronization Editor Basics of target system synchronization Setting up synchronization
Starting the Synchronization Editor Creating a synchronization project Configuring synchronization
Setting up mappings Setting up synchronization workflows Connecting systems Editing the scope Using variables and variable sets Setting up start up configurations Setting up base objects
Overview of schema classes Customizing the synchronization configuration Checking the consistency of the synchronization configuration Activating the synchronization project Defining start up sequences
Running synchronization Synchronization analysis Setting up synchronization with default connectors Updating existing synchronization projects Script library for synchronization projects Additional information for experts Resolving errors when connecting target systems Configuration parameters for target system synchronization Configuration file examples Glossary

How does dependency resolution work?

Dependencies can arise between schema classes that require synchronization stepsClosed to be repeated. For example, object references can not be set until the reference object has been added. Dependencies can also arise between schema properties within a schema class.

Figure 9: Example of a workflow with dependent schema classes and schema properties

One Identity Manager can automatically resolve such dependencies. In this case, the synchronizationClosed steps are group together such that the referenced objects are synchronized first and them the dependent objects next. If dependencies exist within a schema class, additional synchronization steps are inserted to synchronize the dependent schema properties. The final sequence of synchronization steps can be viewed in the report "Execution Plan".

NOTE: If dependencies exist between schema classes, the schema classes must be synchronized by the same workflow so that dependencies can be automatically resolved.

Figure 10: Example of a workflow with automatic dependency resolution

To set up automatic resolution of dependencies

Use automatic dependency resolution by default. Only select manual dependency resolution if individual dependencies cannot be resolved automatically. This might be necessary, for example, if two objects reference each other as mandatory properties.

NOTE: If dependency resolution is set to "Manual", One Identity Manager does not check whether dependencies exits between schema classes and schema properties during synchronization. The synchronization steps are processed sequentially in the order displayed in the workflow view.

Synchronization exits with an error if dependencies exist that cannot be resolved!

To resolve dependencies manually

  1. Find the schema properties between which dependencies exist.
  2. Create a workflow with synchronization steps which take the following criteria into account:
    1. Synchronization steps which synchronize independent and references objects.

      Property mappingClosed rules for dependent schema properties must be excluded for this.

    2. Synchronization steps which reference dependent objects.

      Property mapping rules for dependent schema properties must be included for this.

  3. Specify the synchronization step sequence such that all synchronization steps for a) are executed first and them the synchronization steps for b).
  4. Edit the workflow properties. Select the following option:
    Dependency resolution: Manual

    For more information, see How to edit a workflow.

Related topics

Unresolvable references

If a reference object does not exist in the One Identity Manager database, the object reference cannot be resolved by synchronizingClosed. Unresolvable object references are written in a buffer called the data store (table DPRAttachedDataStore). This ensures that these references remain intact and are not deleted in the target system by provisioning.


An Active Directory group has an account manager, which owns a domain not in the current synchronization run. The account manager is not in the One Identity Manager database either.

Synchronization cannot assign an account manager. In order to retain the assignment, the object reference is saved with the account manager's distinguished name in the data store.

During each synchronization One Identity Manager tries to clean up the data store. If referenced objects in the One Identity Manager database exist, the references can be resolved and the entries are deleted from the data store. The data store is cleaned up depending on the synchronization type (with or without revision filter) and the maintenanceClosed mode.

Table 22: Maintenance for unresolved object references
Maintenance mode Synchronization without revision filer Synchronization with revision filer
The following applies depending on the maintenance mode: Object references of all synchronization objects are cleaned up if they exist in the One Identity Manager database. Only object references for modified objects are cleaned up.
No maintenance There is no additional task of clearing up the data store.
Always synchronize affected objects No effect. The filter is removed on objects with unresolved references. Therefore, references are also cleaned if the objects have not been changed since the last synchronization.
Full maintenance after every synchronization One Identity Manager tries to resolve object references following synchronization. As a result, unresolved references are processed that arose during this synchronization run. One Identity Manager tries to resolve object references following synchronization. As a result, unresolved references are processed that arose during this synchronization run. Object references that were not modified are also cleaned up.

You can enter the number of retries for resolving object references. It may be necessary to try several times to resolve an object if it mapsClosed a hierarchy with several levels. One hierarchy level at a time can be resolved with each attempt to resolve an object.

To set up maintenance mode

NOTE: One Identity Manager supplies a scheduled process plan, which regularly cleans up the contents of the table DPRAttachedDataStore. Object entries, which no longer exist in the One Identity Manager database are deleted. The process plan is executed during daily maintenance.
Related topics

Direction of synchronization and mapping

To synchronizeClosed a target system with One Identity Manager, you must specify which of the connected systems is the data master. Specify the master system in the synchronization configuration with the direction of synchronizationClosed. The direction in which schema properties are mappedClosed may differ from this. Therefore, the permitted mapping direction must be given in the schema properties mapping.

Table 23: Direction of synchronization
Defined on Direction of synchronization specifies
Start configurationClosed In which direction a specific synchronization is executed
WorkflowClosed In which direction synchronizations are executed
synchronization step

By which synchronization direction the step is executed

Table 24: Permitted mapping direction
Defined on Specifies the mapping direction
Mapping By which synchronization direction property mapping rules are used
Property mapping ruleClosed By which synchronization direction this property mapping rule is used

One Identity Manager synchronizes two connection systems in the direction given in the start up configuration or in the workflow. A synchronization step is only executed in this case, if the direction of synchronization stored with the step matches with the direction of the current synchronization. If the mapping direction stored with the mapping corresponds to the current direction of synchronization, the system object from this schema class are synchronized. Thus, One Identity Manager checks which property mapping rule can be used in the current synchronization direction. This property mapping rule is ignored if the mapping direction of the property mapping rule differs from the current direction of synchronization.

Figure 11: Example showing effect of specified synchronization direction and permitted mapping direction

Related topics

Mapping against the direction of synchronization

For certain schema properties, it may be necessary to copy the schema property value immediately from the connected system into the master synchronizationClosed system each time synchronization is run. There is a property mappingClosed rule for these schema properties whose direction of mapping is opposite to the direction of synchronizationClosed. These rules are not executed by default. To transfer these schema property values during synchronization, you must force execution of these rules. This behavior is configured in the property mapping rules.

  • The Detecting rogue modifications option is disabled on the property mapping rule.

To force mapping a schema property against the direction of synchronization

Property mapping rules with this option set are executed after the synchronization stepClosed is completed. This copies changes from the connected system against the direction of synchronization into the master system.

Synchronization Sequence

  1. All property mapping rules whose mapping direction is the opposite to the direction of synchronization are ignored whilst a synchronization step is being executed. Property mapping rules whose mapping direction corresponds to the direction of synchronization are run.
  2. All changes to the connection system are saved when the synchronization step is complete.
  3. All property mapping rules with the option Force mapping against direction of synchronization set are executed again. For those schema properties involved, the changes are copied from the connected system into the master system.

    NOTE: The property mapping rules are also rerun after completion of the synchronization step if there are no processing methods given in the synchronization step.

Use the Force mapping against direction of synchronization option for schema properties that cannot be edited in the master system due to technical limitations.

NOTE: This option is also taken into account when object changes are provisioned.

An Active Directory environment should be administrated through One Identity Manager. One Identity Manager is the master system for synchronizing both systems. The user account object GUIDs are, however, not mapped in One Identity Manager but in the Active Directory environment. This means the mapping direction is different for a user account object GUID. To copy the object GUID from the target system to One Identity Manager during synchronization, the mapping must be forced in the opposite direction of synchronization for this schema property.

Table 25: Synchronization configuration

Configuration Setting


Direction of Synchronization:

To the target system

Property mapping ruleClosed for schema properties:

ADSAccount.ObjectGUID - User.ObjectGUID

Mapping directionClosed:

To the One Identity Manager

Force mapping against direction of synchronization


Synchronization Sequence

Scenario: A new Active Directory user account was added in One Identity Manager.

  1. The user account is added in the target system through synchronization.
  2. The property mapping rule for the object GUID is ignored because of the opposing the mapping direction.
  3. Once all property mapping rules of the synchronization step have been processed, the user account is saved in the target system. A value is calculated in the target system for User.ObjectGUID.
  4. Once the synchronization step is complete the property mapping rule for the object GUID is run again. The object GUID is copied from Active Directory to One Identity Manager.
Related topics
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating