Map User Attributes

LDAP Authorization User Guide

LDAP Connection Error: "No user accounts were found"

The LDAP connection error "No user accounts were found" can occur if the LDAP connection has an incorrect base DN, search contexts, or username attribute mapping. This error can result from any of the following flaws in the configuration of the Lightweight Directory Access Protocol (LDAP) connection: The Base DN is incorrect. The Search Contexts does contain valid usernames. The Username attribute mapping is not set to the appropriate value. Mirth® Connect by NextGen Healthcare identifies user accounts on the LDAP server by looking for objects that contain the Username attribute. For Active Directory, the typical Username attribute is sAMAccountName. For other LDAP servers such as OpenLDAP, a common Username attribute is uid. Username Attribute in LDAP Attribute Mapping These settings are all located on the LDAP Authorization tab. Parent topic: Troubleshooting Connection Errors Related tasks Set Up the LDAP Connection Filter User Accounts Map User Attributes

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

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

Map User Accounts to Roles

Map organizational units, groups, and individual users from the Lightweight Directory Access Protocol (LDAP) directory to specific roles in Mirth® Connect by NextGen Healthcare. Before you begin The User Authorization plug-in must be installed so that the Role column appears in the Search Contexts table. By default, the LDAP Authorization plug-in does not assign roles to user accounts from the LDAP directory. You can manually assign roles in the Search Contexts table. If you have already done so, create or modify roles on the Role-Based Access Control tab. Role-Based Access Control tab Select the LDAP Authorization tab. To assign roles to organizational units (OU), groups, or specific users in the LDAP directory, set Manage Roles to Yes. Manage Roles option In the Role column for each entry, select the role to assign to the users that are listed in the DN column. To assign multiple roles to the same OU, group, or user, create multiple entries with the same DN value but different Role v

LDAP Authorization User Guide

LDAP Connection Error: "An error occurred / No route to host"

The Lightweight Directory Access Protocol (LDAP) connection error "An error occurred / No route to host" can indicate an incorrect host name or a network connection problem. The address entered in the Host field may be incorrect, or Mirth® Connect by NextGen Healthcare is unable to access address on its network. The connection is being tested between the server and the LDAP server. If you are able to access the LDAP server at a given host name from your local machine, it is possible that Mirth® Connect by NextGen Healthcare does not recognize that host name. Parent topic: Troubleshooting Connection Errors

Map User Attributes

Recommendations

LDAP Connection Error: "No user accounts were found"

LDAP Authorization in Mirth® Connect by NextGen Healthcare

Filter User Accounts

LDAP Connection Error: "An error occurred"

Map User Accounts to Roles

LDAP Connection Error: "An error occurred / No route to host"

Map User Attributes

LDAP Connection Error: "No user accounts were found"

LDAP Authorization in Mirth® Connect by NextGen Healthcare

Filter User Accounts

LDAP Connection Error: "An error occurred"

Map User Accounts to Roles

LDAP Connection Error: "An error occurred / No route to host"