Configure options for encrypted communication between Mirth® Connect by NextGen Healthcare and a Lightweight Directory Access Protocol (LDAP) server.
Mirth® Connect by NextGen Healthcare can communicate with a Lightweight Directory Access Protocol (LDAP) server using an encrypted connection. You can set options to encrypt the LDAP connection.
- In the LDAP Configuration section, set Encryption to one of the following:
- None: No encryption is performed.
- STARTTLS: Start with Transport Layer Security (TLS) and upgrade to an encrypted connection. Typically, LDAP servers use port 389 for TLS.
- SSL: Use Secure Sockets Layer (SSL) protocol. Typically, LDAP servers use port 636 for SSL.
- Set Certificate Validation to one of the following:
- Enabled: Mirth® Connect does not connect to the LDAP server if the server presents an SSL certificate that is not trusted. For the connection to succeed, you need to first import the LDAP server public SSL certificate.
- Disabled: Mirth® Connect trusts any certificate presented by the LDAP server.
- Set Hostname Verification to one of the following:
- Enabled: Mirth® Connect does not connect to the LDAP server if the host name presented in the LDAP server SSL certificate does not match the host name of the LDAP server. This option protects Mirth® Connect against person-in-the middle attacks.
- Disabled: The connection is allowed even if the host name in the certificate does not match the host name of the LDAP server.
Note: Disable the Hostname Verification option only if Mirth® Connect and the LDAP server are on the same network and the network is secured.
