Configuration Guide
Configuration Guide
Breadcrumbs

Synchronization Configuration Objects

For each Synchonization Configuration Objects , there is a dedicated page to understand in details how they can be configured and for what :

  • Application

    Application is the main synchronization configuration entry point. An "Application" conceptually designates a remote system, external to Synchronization Service, exposing a repository of accounts (or organizations), such as a LDAP directory, or a CSV file. Usually an Application is configured to perform either “inbound” operations, such as importing a CSV file, or “outbound” operations, such as provisioning an LDAP directory. Technically, the same Application could be configured to perform both inbound and outbound operations, but this is a rare functional case, because most of the time there is a single “authoritative side”. For example, a HR CSV file is the unique “source of truth” to create or update IM Identities, and in turn IM Identities are the source of truth to create or update accounts in a LDAP directory. The Application namely defines “attribute mappings”, i.e. how to map an IDM object’s attributes (such as a last name) with the attributes of an object belonging to a remote system, such as the columns of a CSV file or the attributes of an LDAP account. Attribute mapping rules may vary according to the type of an IDM object, e.g. for an IDM object of type “employee” the mapped attributes could differ from an IDM object of type “partner”. An Application's population may thus be divided into several IDM Object Types, hence the possible diversification, within an Application's configuration, of sub-configurations per Object Type, as shown in the schema below:

  • Application Profile

    An Application Profile targets a specific Application, e.g. the "Trade" Active Directory. Having an Application Profile always implies having an account on the target Application.

  • Pre-Synchronization Tasks

    Pre-Synchronization Tasks configures settings applied before executing the Synchronization Task per se. Currently, the only purpose of a Pre-Synchronization task is to validate a CSV file signature before executing the import. To do this, the client signs and uploads the CSV import file to the Memority exchange server. Before running the import, Memority checks that the CSV file has indeed been signed by the client, and that the signature is valid.

  • Provisioning Task Definition

    Provisioning Task Definition configures the settings used to launch provisioning tasks, namely by specifying the target Application id.

  • Orchestration Task

    An Orchestration Task chains the execution of some of those tasks, by defining dependencies between tasks, and conditions to trigger or skip their execution.