Chat now with support
Chat with Support

Identity Manager 8.0 - Administration Guide for Connecting to G Suite

Managing G Suite Setting Up G Suite Synchronization Base Data for Managing G Suite Troubleshooting Appendix: Configuration Parameter for Managing G Suite Appendix: Default Project Templates for G Suite Appendix: Editing System Objects

Speeding Up Synchronization with Revision Filtering

Speeding Up Synchronization with Revision Filtering

SynchronizationClosed with G Suite does not support revision filtering.

Post-Processing Outstanding Objects

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.

Objects marked as outstanding:

  • Cannot be edited in One Identity Manager.
  • Are ignored by subsequent synchronization.
  • Must be post-processed separately in One Identity Manager.

Start target system synchronization to do this.

To post-process outstanding objects

  1. Select the category G Suite | Target system synchronization: G Suite.

    All tables assigned to the target system type G Suite as synchronization tables are displayed in the navigation view.

  1. Select the table whose outstanding objects you want to edit in the navigation view.

    This opens the target system synchronization form. All objects are shown here that are marked as outstanding.


    To display object properties 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 one of the following icons in the form toolbar to execute the respective method.
    Table 12: Methods for handling outstanding objects





    The object is immediately deleted in the One Identity Manager. Deferred deletion is not taken into account. The "outstanding" label is removed from the object.

    Indirect memberships cannot be deleted.


    The object is added in the target system. The "outstanding" label is removed from the object.

    The method triggers the event "HandleOutstanding". This runs a target system specific process that triggers the provisioning process for the object.


    • The table containing the object can be published.
    • The target system connector has write access to the target system.


    The "outstanding" label is removed from the object.

  3. 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

  • Deactivate in the form toolbar.

You must customize synchronization to synchronize custom tables.

To add tables to the target system synchronization.

  1. Select the target system type G Suite in the result list.
  2. Select Assign synchronization tables in the task view.
  3. Assign custom tables whose outstanding objects you want to handle in Add assignments.
  4. Save the changes.
  5. Select Configure tables for publishing.
  6. Select custom tables whose outstanding objects can be published in the target system and set the option Publishable.
  7. 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 option Connection is read only must no be set for the target system connection.

Configuring Memberships Provisioning

Configuring Memberships Provisioning

Memberships, for example, 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 will probably 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 users accounts in the property Members of a group).
  • Memberships can be modified in either of the connected systems.
  • A provisioning workflow and provisioning processes are set up.

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

  1. Start the Manager.
  2. Select the category G Suite | Basic configuration data | Target system types.
  3. Select Configure tables for publishing.
  4. Select the assignment tables for which you want to allow separate provisioning. Multi-select is possible.
    • The option can only be set for assignment tables whose base table has a column XDateSubItem.
    • Assignment tables, which are grouped together in a virtual schema property in the mapping, must be labeled identically.
  5. Click Enable merging.
  6. Save the changes.

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 SystemClosed SynchronizationClosed Reference Guide.

Help for Analyzing Synchronization Issues

Help for Analyzing Synchronization Issues

You can generate a report for analyzing problems which occur during synchronization, for example, insufficient performance. The report contains information such as:

  • Consistency check results
  • Revision filterClosed settings
  • ScopeClosed applied
  • Analysis of the synchronization buffer
  • Object access times in the One Identity Manager database and in the target system

To generate a synchronization analysis report

  1. Select the menu Help | Generate synchronization analysis report and answer the security prompt with Yes.

    The report may take a few minutes to generate. It is displayed in a separate window.

  2. Print the report or save it in one of the available output formats.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating