Authenticate to the CMS using Secure LDAP
Version: CMS 10, 10.x, CMS 8, 8.x, CMS 9, 9.x
October 9, 2013
Last updated: 1/30/2021
The Ingeniux CMS natively supports authentication via LDAP (Lightweight Directory Access Protocol). However, organizations that wish to authenticate using Secure LDAP (also known as LDAP over SSL) must deploy additional code for the authentication to work.
- Administrative access to the Content Management Server (CMS).
- An LDAP server that supports secure LDAP
- Appropriate firewall rules to allow the CMS server to communicate with the LDAP server.
- Identify information needed to connect to the LDAP server. Typical information includes:
- Server name/IP (Example: ldap.customer.com)
- Search base (Example: ou=people,dc=customer,dc=com)
- Bind Account/Lookup Account credentials (if applicable)
- Port for Secure LDAP communication (636 by default)
- Download the following ZIP file: secure-LDAP-code (7KB).
- On your CMS Server, browse to the \xml\App_Code directory.
- In this location, back up the LDAPMembershipProvider.cs and LDAPDirectory.cs files.
- Unzip the files LDAPMembershipProvider.cs and LDAPDirectory.cs from the ZIP file to the \xml\App_Code directory, overwriting the existing files.
- Stop the CMS Application Pool within IIS Manager.
- Open \local-appsettings.config and make sure the userdomain value is blank. Save the file.
- Open \local-connection-strings.config and configure the connection string to your LDAP server and save the file.
- Example: .
- Open \local-membership.config and modify the file to reflect the information below. Bold indicates values that may be different for your environment:
- Restart the CMS Application Pool.
If you are unable to authenticate successfully with the CMS after following the above steps (you recieve a red error message: "Invalid username or password. Please try again.), there are several troubleshooting steps you can take.
- Download a Windows LDAP browser to your Content Management Server. Ingeniux recommends the free Softerra LDAP Browser.
- Using the software, replicate your connection information that you put in the CMS configuration files and see if you can bind sucessfully and get a list of users.
- If you cannot bind, note the error message that the software outputs. There may be a connection problem between the Content Management Server and the LDAP server, or the connection information may not be correct.
- If you can bind using the software, but you cannot authenticate with the CMS, there is a problem with your CMS authentication configuration.
- Make sure you enter all connection information exactly as you did in your LDAP browser.
- Make sure you copied the files in secure-LDAP-code.zip as described in steps three and four above.
- Turn on trace logging to get additional error information:
- Open \web.config.
- Search for the following line:
- Change pageOutput and enabled to true so that the line looks like this:
- Now, after logging into the CMS, additional error information should be shown, allowing for more specific troubleshooting.
Support for native Secure LDAP authentication is expected to be added in a future release of the Ingeniux CMS.