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 |
| YES | The task identifier. | - |
name |
| YES | The task name. | - |
description |
| NO | The task description. | - |
- | 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:
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, | - |
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 |
| YES | The key of the Setting containing the X509 certificate Base64 used to verify the signature. | - |
extension |
| 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, | p7s |
Example
Here is a simple XML representation of a Pre-Synchronization Tasks.