Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Confluence LDAPs - | How to Setup TLSv1 for LDAP Access ?



wanna Upgrade to Confluence 7.1.0 from 6.15.x.
Build a clone to check.
But the LDAPs connection to MS Active Directory did not work.

Got this error:

nested exception is javax.naming.CommunicationException: adserver.domain:tld [Root exception is The server selected protocol version TLS10 is not accepted by client preferences [TLS12, TLS11]]


Using OpenJDK 11
The Active Directory did only use TLSv1
How to setup that LDAPs connection work with TLSv1


Tryed:  in JDK Dircertoy: conf/security/


But this did not work.


7 answers

Same here, trying to connect Confluence 7.1.0 to Jira 8.5.1 and getting the TLS error with AdoptOpenJDK 11

Same here, worked before with 7.0.2, now with 7.2.0 it doesn't.

I had the same probleme with confluence 7.4.0 connecting to jira 8.5.4 with adoptjdk 11

I reenabled tls V1 by changing  the following line in

CATALINA_OPTS="-Djdk.tls.server.protocols=TLSv1.1,TLSv1.2 -Djdk.tls.client.protocols=TLSv1.1,TLSv1.2 ${CATALINA_OPTS}"



CATALINA_OPTS="-Djdk.tls.server.protocols=TLSv1,TLSv1.1,TLSv1.2 -Djdk.tls.client.protocols=TLSv1,TLSv1.1,TLSv1.2 ${CATALINA_OPTS}"

That worked for me but doesn't feel good.

Our Problem was that the Apache proxy was still using the unsecure TLSv1.

After reconfiguring our proxy to use just the newer tls versions, the above modification wan't necassary anymore

Even though my Windows server isn't 2008 (it's 2012 R2), adding server support for TLS 1.2 in the registry fixed it for me:

I was wrong. It helped, but my problem is not all the way fixed.

@Benjamin Heublein 

Did you mean only change the ../bin/

CATALINA_OPTS="-Djdk.tls.server.protocols=TLSv1,TLSv1.1,TLSv1.2 -Djdk.tls.client.protocols=TLSv1,TLSv1.1,TLSv1.2 ${CATALINA_OPTS}"

did not work me - login fail


2020-05-14 09:14:48,833 ERROR [https-jsse-nio-8191-exec-21] [crowd.manager.application.ApplicationServiceGeneric] authenticateUser Directory 'LDAP-Server' is not functional during authentication of 'myuser1'. Skipped.

In Admin Panel I got this error if test connection:

Grundlegende Verbindung testen : Fehlgeschlagen srv01.domain.tld:636; nested exception is javax.naming.CommunicationException: srv01.domain.tld:636 [Root exception is PKIX path building failed: unable to find valid certification path to requested target]

sorry my fail - forgot the cacertfile in the new jdk!


It work for me !

  thanks a lot !

Suggest an answer

Log in or Sign up to answer
Community showcase

All you wanted to know about customer support KPIs

When working in customer support, it’s crucial to calculate, analyze and monitor specific numbers, called KPIs (Key Performance Indicators). They go hand-in-hand with customer satisfaction, problem d...

107 views 1 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you