Configuration Guide
Configuration Guide
Breadcrumbs

Pre-Synchronization Tasks

Definition

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.

Configuration

🎯

You can access the Pre-Synchronization Tasks configuration :

  • by clicking on "Synchronization" â†’ "Pre-Synchronization Tasks"

  • by clicking on "System" â†’ "Configurations"->”Synchronization Service” and perform an import/export.

Properties

Property Name

Type

Mandatory

Description

Values (default value in bold)

id

String

YES

The task identifier.

-

name

String

YES

The task name.

-

description

String

NO

The task description.

-

fileSignatureVerificationDefinition

-

NO

To ensure the integrity and the origin of a deposited CSV file, it is possible to verify the signature of the CSV file before importing it. Only the CMS “detached” signature standard is currently supported, as specified by RFC 5652.

2 files must be deposited:

  • the main CSV file to import

  • the “detached” CSV signature file, which is verified by Memority

It is supposed that the signature file has the same path name as the main file plus a configurable extension, which would give, for example, RH-extract.csv.p7s if the main file is RH-extract.csv.

-

fileSignatureVerificationDefinition

This section configures the settings enabling to verify the detached signature of a CSV file (see above).

Property Name

Type

Mandatory

Description

Values (default value in bold)

certificateSettingKey

String

YES

The key of the Setting containing the X509 certificate Base64 used to verify the signature.

-

extension

String

YES

The detached signature file extension.

It is supposed that the signature file has the same path name as the main file plus a configurable extension, which would give, for example, RH-extract.csv.p7s if the main file is RH-extract.csv.

p7s

Example

Here is a simple XML representation of a Pre-Synchronization Tasks.

Pre-Synchronization Tasks
XML
<dmn:SynchronizationTaskPreProcessingDefinition id="PreProcessingTask">
  <name>PreProcessingTask</name>
  <description>Description of PreProcessingTask</description>
  <fileSignatureVerificationDefinition>
    <certificateSettingKey>key.of.signing.certificate</certificateSettingKey>
    <extension>p7s</extension>
  </fileSignatureVerificationDefinition>
</dmn:SynchronizationTaskPreProcessingDefinition>
  • Import Task

    An Import Task allows either an end user or the system (in the case of a scheduled import) to launch a data import using a CSV file or a REST API.

  • Reconciliation

    Reconciliation allows to compare the content of a remote application's repository with the IDM repository. The reconciliation task starts by scanning all the application's objects (accounts, organizations...), detecting changes regarding the IDM state; new applicative accounts added, accounts that no longer exist (i.e. removed by the application's administrator), accounts modified. Reconciliation is usually executed as a scheduled task.