Enable Debug Logging for LDAP Activity

LDAP Authorization User Guide

LDAP Connection Error: "An error occurred"

The Lightweight Directory Access Protocol (LDAP) connection error "An error occurred" indicates an error that Mirth® Connect by NextGen Healthcare does not recognize. An error occurred that Mirth® Connect by NextGen Healthcare does not recognize. Check to see if an error message was returned by the Lightweight Directory Access Protocol (LDAP) server. If so, the errors looks something like this: LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 701, v1db0 Make a note of the number specified in data <number>. In the preceding example, the number is 701, which is referred to as an LDAP result code. You can view definitions of LDAP result codes at the LDAP Result Code Reference page on ldap.com. If an LDAP error message is not shown, enable debug logging so that additional information can be collected the next time the error occurs. Parent topic: Troubleshooting Connection Errors Related concepts Enable Debug Logging for LDAP Activity

LDAP Authorization User Guide

LDAP Authorization in Mirth® Connect by NextGen Healthcare

When the Lightweight Directory Access Protocol (LDAP) extension is installed, users can log on to Mirth® Connect by NextGen Healthcare using credentials that are controlled by a separate LDAP directory. The connection between Mirth® Connect and the Lightweight Directory Access Protocol (LDAP) server can be encrypted if needed for security. You can use the Role-Based Access Control extension for Mirth® Connect to assign roles to specific groups of user accounts in the LDAP directory. The LDAP extension is designed to work with LDAP directory services such as: Active Directory OpenLDAP™ ApacheDS™ You can configure LDAP integration in Mirth® Connect in Settings > LDAP Authorization: LDAP Configuration section When LDAP authorization is enabled, only user accounts that exist in the LDAP Directory are permitted to log on to Mirth® Connect. Any local Mirth® Connect user accounts (listed under Users in Mirth® Connect) are disabled. These accounts are re-enabled if LDAP authorization is later

LDAP Authorization User Guide

Filter User Accounts

Specify which organizational units, groups, or individual users in a Lightweight Directory Access Protocol (LDAP) server are allowed to log on to Mirth® Connect by NextGen Healthcare. By default, all users within the base distinguished name (DN) can log on to Mirth® Connect by NextGen Healthcare. To adjust which users are able to log on to Mirth® Connect, you can add user groups to the Search Contexts table. When the table is populated, log ons are permitted only for the organizational units (OUs), groups, or individual users listed in this table. Search Contexts Table Open the LDAP Configuration page in Mirth® Connect. Your users with provisioned access are listed in the Base DN field and the Search Contexts field. To add an entry, select Add next to the Search Contexts field. To delete an entry, select the entry, then select Delete. To specify the users that are allowed by a particular entry, do the following: Select an entry. Select the folder DN folder icon icon at the right of the

LDAP Authorization User Guide

Troubleshooting Connection Errors

Lightweight Directory Access Protocol (LDAP) connection errors can appear in the Mirth® Connect by NextGen Healthcare server log. They can also appear when you test the connection in the LDAP Authorization settings panel. A Connection Error in the Test Connection Window In some cases, you can gain additional information about an error condition by enabling debug logging for LDAP activity. LDAP Connection Error: "Admin User DN or Admin Password is invalid" The Lightweight Directory Access Protocol (LDAP) connection error "Admin User DN or Admin Password is invalid" includes a data number that indicates why the credentials were rejected. LDAP Connection Error: "An error occurred" The Lightweight Directory Access Protocol (LDAP) connection error "An error occurred" indicates an error that Mirth® Connect by NextGen Healthcare does not recognize. LDAP Connection Error: "An error occurred / No route to host" The Lightweight Directory Access Protocol (LDAP) connection error "An error occurred

LDAP Authorization User Guide

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). To set up Lightweight Directory Access Protocol (LDAP) integration, perform these steps. In the LDAP Configuration section, open the LDAP Authorization tab. Set LDAP Enabled to Yes. This option is initially disabled. Enabling LDAP Integration 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. Host Address and Port 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. Base DN Enter the Admin user DN (also called the Bind DN) and the password. These are the credentials that Mirth® Conn

LDAP Authorization User Guide

Enable Encryption

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. LDAP Configuration 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 t

Enable Debug Logging for LDAP Activity

Recommendations

LDAP Connection Error: "An error occurred"

LDAP Authorization in Mirth® Connect by NextGen Healthcare

Filter User Accounts

Troubleshooting Connection Errors

Set Up the LDAP Connection

Enable Encryption