Legacy Knowledge Base
Published Jun. 30, 2025

Unable to bind to the LDAP server javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]

Written By

Kanchan Bisht

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • Unable to connect to Open LDAP in DXP due to the following UI error blobid0.png

Environment

  • Liferay DXP 7.4

Resolution

  • These errors typically occur when Liferay is unable to communicate with LDAP or when mapping mistakes are made.

    • As a result, please ping both servers to ensure that they can communicate with one another. If they are, please check to see if any firewall settings are blocking the specified port.

  • However, in this case, the principal's CN was incorrect in the connection section at the Liferay end. Three dc have been used, but in principal, these have not been mentioned and have been configured as follows:
    Principal's CN> cn=admin,ou=people
    • As a result, the correct mapping would be as follows: users should replace 'ou=people' with
      Principal's CN> cn=admin,dc=xyz,dc=abc,dc=com
    • The values abc and xyz are only for demonstration purposes, please see the actual values on the OpenLDAP side.     

Additional Information

  • This error can also occur when the LDAP user and/or password are incorrect. The same error is generated if the Distinguished name (dn) value is incorrect.
Did this article resolve your issue ?

Legacy Knowledge Base