Set Up the LDAP Connection

To set up Lightweight Directory Access Protocol (LDAP) integration, you must enable LDAP, enter a host address and port number, and enter the base distinguished name (DN).

1. In the LDAP Configuration section, open the LDAP Authorization tab.
2. Set LDAP Enabled to Yes.

   This option is initially disabled.

   

3. Enter the host address and port of your LDAP server.
   The standard port used by LDAP servers is typically port 389. When Secure Sockets Layer (SSL) protocol is enabled, the port number typically is 636.

   

4. Enter the base distinguished name (DN).
   The base DN is the root DN under which all operations and user searches take place. If this field is left blank, Mirth® Connect by NextGen Healthcare attempts to detect the base DN from the Admin user DN.

   

5. Enter the Admin user DN (also called the Bind DN) and the password.

   These are the credentials that Mirth® Connect uses to access the LDAP server. These credentials must have the privilege to execute searches for other users in the LDAP directory. The account should typically be an administrative-level account.

   

   • If you previously configured these credentials, the password field is blank.
   • Typically, you need to re-enter the password if you want to change it.
   • You also need to re-enter the password if the Mirth® Connect internal encryption key changes or if the Mirth® Connect configuration is restored from a backup that used a different encryption key.
6. Provide a recovery username and password that can be used if the remote LDAP server is unavailable or inaccessible by Mirth® Connect.
   

   When LDAP authorization is enabled in Mirth® Connect, only usernames and passwords in the LDAP directory can be used to log on. If the LDAP server becomes inaccessible for some reason, this one local recovery account can be used to log on and fix (or disable) the LDAP configuration in Mirth® Connect.

   • If you configured these credentials previously, the password field is blank.
   • Typically, you need to re-enter the password if you want to change it.
   • You also need to re-enter the password if the Mirth® Connect internal encryption key changes or if the Mirth® Connect configuration is restored from a backup that used a different encryption key.

   Note: If the LDAP directory is inaccessible, this account is the only username and password that can log on to Mirth® Connect.
7. Select Test Connection to verify that the configuration is correct.
   

   The Test Connection window indicates whether the connection succeeded.

   

8. Verify that the user accounts listed are those you want to allow access to Mirth® Connect by NextGen Healthcare.
   The table shows the result of the attribute mappings configured in the LDAP Attribute Mapping section. The Attribute list shows attributes that are not currently mapped to any user fields in Mirth® Connect.
9. If any of the user field mappings have incorrect values (for First Name, Last Name, Email, and so on), make the appropriate changes in the LDAP Attribute Mapping section. Refer to the list of unmapped attributes if needed.