Issue Summary

After configuring an LDAPS directory, in the Test Remote Directory Connection page (Save and Test), the following error message will be presented: 

Test user can authenticate : Failed
org.springframework.ldap.CommunicationException: ldap.atl-cd.net:636; nested exception is javax.naming.CommunicationException: ldap.atl-cd.net:636 [Root exception is java.lang.ClassNotFoundException: com.atlassian.crowd.directory.ssl.LdapHostnameVerificationSSLSocketFactory not found by com.atlassian.crowd.embedded-crowd-admin-plugin [26]]

The synchronization seems to work normally if the LDAPS server is correctly configured; however, the test will fail. This is similar to the bug from Bitbucket: BSERV-19728

Steps to Reproduce

1. Start a Jira 10+ instance;
2. Configure an LDAPS directory (Port 636);
3. Click on the "Save and Test" button;
4. Enter the username and password > Test Settings
5. The following error message will be presented: 

   [Root exception is java.lang.ClassNotFoundException: com.atlassian.crowd.directory.ssl.LdapHostnameVerificationSSLSocketFactory not found by com.atlassian.crowd.embedded-crowd-admin-plugin [26]]
   

Expected Results

The test will work without the ClassNotFoundException error.

Jira 9.12.17:

Actual Results

The following error message will be presented: 

[Root exception is java.lang.ClassNotFoundException: com.atlassian.crowd.directory.ssl.LdapHostnameVerificationSSLSocketFactory not found by com.atlassian.crowd.embedded-crowd-admin-plugin [26]]

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available