connection between ACtive directory -Ldap and Crowd using ssl

Deleted user December 15, 2014

There was a problem communicating with the LDAP server: simple bind failed: 192.168.0.13:636; nested exception is javax.naming.CommunicationException: simple bind failed: 192.168.0.13:636 [Root exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching 192.168.0.13 found.]

1 answer

0 votes
Caspar Krieger
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 15, 2014

Taking a random guess at your situation: if you're using LDAPS (accessing LDAP over TLS), the certificate provided by your LDAP server will be verified against the host you're connecting to. Your certificate is probably for a particular domain, but you're connecting to the LDAP server by its IP address. Try connecting to the LDAP server via the domain that the certificate is for instead.

If that doesn't help, please raise a support request and our friendly support team will help you collect information so we can troubleshoot.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events