Active Directory Integration

Our system’s LDAP connector connects to your LDAP servers and pulls data from your directory to automatically create email signatures directly on Dynasend.

Multiple connections are allowed to map different groups of users to different signature templates.

There’s a mapper (this is currently a JSON dictionary) to define how LDAP fields tie to each email signature fields.

To enable this connection you’ll need to provide credentials for the LDAP server:

  • username: string To connect to your LDAP server, a username and password is required to be able to query and run operations on your server(s). The username option must be a user’s Distinguished Name. If however you are connecting to an Active Directory server, you may use: userPrincipalName ( Down-Level Logon Name (DOMAIN\username)
  • password: string
  • hosts: string[] list The hosts option is an array of IP addresses or host names located on your network that serve an LDAP directory.
  • base_dn: string A ‘Distinguished Name’ is a string based identifier in LDAP that is used to indicate hierarchy. Each object in your domain is assigned a Distinguished Name. This can be used to assign subset of users to templates.
  • port: integer. The port option is used for opening a connection and binding to your LDAP server.
  • follow_referrals: boolean The follow referrals option is a boolean to tell Active Directory to follow a referral to another server on your network if the server queried knows the information your asking for exists, but does not yet contain a copy of it locally.

We offer two levels of AD integration to best meet your needs.

  • AD data always takes precedence: The data reflected in the email signature will always be the most recently received data from AD - our database is overwritten every time we sync with AD.

  • AD data populates user data the FIRST TIME but then users CAN OVERWRITE it: This provides a way of initially populating the Dynasend database with user data (and adding new users as they come on board). This is a “WRITE ONCE” scenario, where after the data is written to our database for the first time, it can then be overwritten by the user via our data entry portal.