サポートと今すぐチャット
サポートとのチャット

Identity Manager 9.1 - 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 Troubleshooting errors when connecting target systems Configuration parameters for target system synchronization Configuration file examples

Toolbars in the log view

The navigation view in the Logs category has its own toolbar.

Table 71: Meaning of icons in the navigation view
Icon Meaning
Reload the data.
Display synchronizationClosed log.
Display provisioning log.
Only display most recent logs. This display logs from within the past 24 hours.
Sort by activation time.
Sort by processing status.

How to display synchronization logs

To display a synchronizationClosed log

  1. In the Synchronization EditorClosed, open the synchronization projectClosed.

  2. Select the Logs category.

  3. Click in the navigation view toolbar.

    Logs for all completed synchronization runs are displayed in the navigation view.

  4. Select a log by double-clicking it.

    An analysis of the synchronization is shown as a report. You can save the report.

To display a provisioning log

  1. In the Synchronization Editor, open the synchronization project.

  2. Select the Logs category.

  3. Click in the navigation view toolbar.

    Logs for all completed provisioning processes are displayed in the navigation view.

  4. Select a log by double-clicking it.

    An analysis of the provisioning is shown as a report. You can save the report.

The log is marked in color in the navigation view. This mark shows you the status of the synchronization/provisioning.

TIP: The logs are also displayed in the Manager under the <target system> > synchronization log category.

Target system synchronization

Objects, which do not exist in the target system, can be marked as outstanding in One Identity Manager by synchronizingClosed. 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 synchronizationClosed to do this.

To post-process outstanding objects

  1. Start the Manager.
  2. Select the <target system type> > Target systemClosed synchronization: <target system type> > <table> category.

    TIP:

    To display object propertiesClosed of an outstanding object

    1. Select the object on the target system synchronization form.

    2. Open the context menu and click Show object.

  1. Select the objects you want to rework. Multi-select is possible.

  2. Click on one of the following icons in the form toolbar to run the respective method.

    Table 72: Methods for handling outstanding objects

    Icon

    Method

    Description

    Delete

    The object is immediately deleted from the One Identity Manager database. Deferred deletion is not taken into account.

    Indirect memberships cannot be deleted.

    Publish

    The object is added to the target system. The Outstanding label is removed from the object.

    This runs a target system specific process that triggers the provisioning process for the object.

    Prerequisites:

    • The table containing the object can be published.

    • The target system connector has write access to the target system.

    • A customClosed process is set up for provisioning the object.

    Reset

    The Outstanding label is removed for the object.

  3. Confirm the security prompt with Yes.

NOTE: By default, the selected objects are processed in parallel, which speeds up 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

  • Disable the icon in the form's toolbar.

For more information about post-processing outstanding objects from connected target systems, see the target system connection guides.

Related topics

Deleting memberships

Membership of user accounts in groups, for example, can result from direct assignment or through inheritance in One Identity Manager. The membership's origin is stored in the XOrigin assignment tableClosed. Inherited memberships cannot be deleted as long as the inheritance source still exists. If inherited memberships are deleted in the target system, they are marked as outstanding by synchronizationClosed, depending on which processing method was selected.

You can differentiate between the following cases of deleting membership through synchronization:

Table 73: Deleting memberships
Membership origin Delete method MarkAsOutstanding method
Only direct The membership is deleted immediately by synchronization. The membership is marked as outstanding by synchronization.
Only inherited The membership is marked as outstanding by synchronization. The membership is marked as outstanding by synchronization.
Direct and inherited The membership is marked as outstanding by synchronization. The reference to direct assignment is removed (value in the XOrigin column is updated). The membership is marked as outstanding by synchronization.

Outstanding memberships must be post-processed separately. You can publish these memberships if the inheritance source still exists or you set the status back and remove the inheritance source.

Example

Pat Identity1 has an Active Directory user account that is a member of the Active Directory group "Backup operators". This membership is loaded into the One Identity Manager database by initial synchronization and saved as direct membership in the ADSAccountInADSGroup table (XOrigin = '1'). Pat Identity1 is member of the business roleClosed "Project A". This business role is assigned to the Active Directory group "Backup operators". Therefore, Pat Identity1 becomes an indirect member of this Active Directory group (ADSAccountInADSGroup.XOrigin = '3'). The group membership is deleted in the target system. The deleted membership is immediately deleted in the One Identity Manager database the next time synchronization is run (ADSAccountInADSGroup.XOrigin = '2'). The membership is marked as outstanding because it remains in the One Identity Manager database due to inheritance. The outstanding membership must be post-processed in target system synchronizationClosed. There are two possible ways to do this:

  1. Assignments to the business role "Project A" are correct.

    The method "Publish" is applied. Membership is re-added to the target system.

  2. Mapping in the target system is correct.
    • The method "Reset status" is applied.
    • The assignment of the Active Directory group to the business role "Project A", or Pat Identity1's membership of this business role must be deleted. The group membership must also be deleted from ADSAccountInADSGroup table.

The method "Delete" cannot be applied.

Related topics
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択