Cannot authenticate to LDAP server via SSL since upgrade to 5.1.1.
Test basic connection : Failed
vanpdc02.impacservices.com:636; nested exception is javax.naming.CommunicationException: vanpdc02.impacservices.com:636 Root exception is java.lang.ClassNotFoundException: com.atlassian.crowd.directory.ssl.LdapHostnameVerificationSSLSocketFactory
Also, in the logs -
Caused by: java.security.cert.CertificateException: No subject alternative DNS name matching impacservices.com found.
at sun.security.util.HostnameChecker.matchDNS(Unknown Source)
at sun.security.util.HostnameChecker.match(Unknown Source)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkIdentity(Unknown Source)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)
I susepct that you are facing the bug described here: https://jira.atlassian.com/browse/JRA-27347
If that is the case then it is just the test that fails, but the LDAPS connection and the synchronisation are actually successful. Therefore I would suggest you start by checking whether the connection and synchronisation are working correctly, rather than just following the error message, and if they aren't then I would suggest that you open a support ticket so that we can investigate the cause of this issue.
All the best,
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot