Syncing certificates (base64 encoded) from ODBC/CSV to AD

Created: 2017-07-26 11:01:00
Modified: 2018-05-01 13:37:31
Tags: Active Directory CSV Custom Mapping Features ODBC Troubleshooting UnitySync

As of UnitySync v2.7, base64 formatted certificate strings can be synced from ODBC or CSV to set an Active Directory (AD) usercertificate.

In order for the Discovery to read the base64 format data correctly, you’ll need to use a optional raw config option:


When set to identify the base64 column, the discovery can read the value and include it in the ldif.txt as base64 encoded format.

For example, let’s say your column containing the base64 string is named CertBase64.

In your source data, the value looks similar to BB4CCBqygAw….etc.

Perform the following steps:

  1. On the Custom tab, click Raw Config.

    • Add this parameter and click Save:


  2. Create a custom object map file if you don’t already have one in use.

    • Add the mapping:


    • Click Save on the custom object map, then Save again to save the selection of the new map file.
  3. Run Discovery.

    • The ldif.txt should include a double colon in the column name:

      CertBase64:: BB4CCBqygAw....etc.

  4. Run Sync. On the destination AD, you should see a valid certificate has been synced.

Share this article:

  1. Directify - Self Service

  2. Mimic - Replication

  3. UnitySync - Sync
  1. emPass - Sync
  1. Profiler
  2. SimpleSync