ServiceUnavailableException Reported When Connecting to LDAP Using SSL

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

When trying to connect to an LDAP Server using SSL, the following error is reported in the log file:

1 2 3 4 5 6 7 8 [console.action.directory.UpdateConnectorConfiguration] example.com:636; socket closed; nested exception is javax.naming.ServiceUnavailableException: example.com:636; socket closed org.springframework.ldap.ServiceUnavailableException: example.com:636; socket closed; nested exception is javax.naming.ServiceUnavailableException: example.com:636; socket closed at org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:210) at org.springframework.ldap.core.support.AbstractContextSource.createContext(AbstractContextSource.java:266) at org.springframework.ldap.core.support.AbstractContextSource.getContext(AbstractContextSource.java:106) at org.springframework.ldap.core.support.AbstractContextSource.getReadOnlyContext(AbstractContextSource.java:125) at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:287) at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:237)

Cause

When using SSL to connect to LDAP, Crowd 2.0.0 and newer versions require the connector URL to use ldaps:// instead of only ldap://.

Resolution

  • In the connector URL field, ensure that the URL string starts with ldaps://

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.