The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira LDAP using SSL test user fails

Paul Cope
Contributor
March 27, 2025

Using an internal JIRA server v10.3.1#10030001

we are getting errors when trying to enable SSL connection for the LDAP lookups.

The initial connection to the server passes but when you test a user lookup it fails with the following error:

 

Test basic connection : Succeeded
Test retrieve user : Failed
org.springframework.transaction.CannotCreateTransactionException: Could not create DirContext instance for transaction; nested exception is org.springframework.ldap.CommunicationException: Loading the socket factory; nested exception is javax.naming.CommunicationException: Loading the socket factory [Root exception is java.lang.ClassNotFoundException: com.atlassian.crowd.directory.ssl.LdapHostnameVerificationSSLSocketFactory not found by com.atlassian.crowd.embedded-crowd-admin-plugin [26]]
Can anyone help please?

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Jim Knepley - ReleaseTEAM
Atlassian Partner
March 27, 2025

Hi @Paul Cope 

You're not alone, and the bug was fixed in 10.3.3.

ref: https://jira.atlassian.com/browse/JRASERVER-78523

 

Paul Cope
Contributor
March 28, 2025

What I dont get is how they class it a a minor bug? How is sending authentication via plain text across the network not a major issue?

Jim Knepley - ReleaseTEAM
Atlassian Partner
March 28, 2025

Atlassian's definition of severity levels is based on customer impact. I imagine they chose to classify LDAPS being broken as a "minor" incident because a workaround existed (use unencrypted LDAP instead).

Paul Cope
Contributor
March 28, 2025

Update to the ticket, upgrading from 10.3.1 to 10.3.4 has fixed the issue. We can now use SSL for LDAP.