Retarus Directory Synchronization Service (DirSync)

Important for Email Security customers using Azure AD

The DirSync Service described in this manual supports local Active Directories (and LDAP compliant systems). If you are using a Microsoft Azure Active Directory, you may use the “Retarus Azure Active Directory Sync” instead (Email Security only). For more information, please refer to the detailed documentation available via the Retarus myEAS portal.

The Retarus Directory Synchronization (“DirSync”) Service facilitates synchronizing customers’ directory data to Retarus, thus simplifying the administration of the Retarus Email Security services for customers. It enables customers to automate the upload of user information such as email addresses, fax numbers etc. from their Active Directory to the Retarus infrastructure.

The DirSync wizard provides support natively for Microsoft Active Directory (AD). However, it also supports standard LDAP communication; therefore, it does also seamlessly interoperate with other LDAP compliant systems.

The service reads the specified LDAP directory at custom- defined intervals, applying any preconfigured LDAP filters in order to obtain only those results required for the Retarus services. This information is then, depending on the Retarus services used, converted to a file format expected by the Retarus infrastructure and sent to Retarus via HTTPS. These files can also be saved on the hard disk for inspection.

The AD information that is to be forwarded to Retarus is by default limited to those attributes required for the service. The AD fields can be selected in the configuration accordingly. Depending on the type of Retarus service used by the customer, the following information is commonly exported from the directory:

More detailed directory information may be required for example if personalization features of Retarus services are used (e.g. Signature/Disclaimer). Directory information such as organizational unit (OU) or group memberships may be leveraged to map users to service profiles.

The Windows service is designed to support more than one Retarus service at the same time. For example, it can be used to administrate both users of the Email Security and Email-to-Fax service simultaneously. Therefore, it’s not required to install the service multiple times with individual configurations in order to allow for multiple services.