How to modify the TLS version Jira uses when connecting as a client

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.

The current article applies when Jira performs secure connections through SSL/TLS as a client (such as LDAPS). For Jira inbound SSL/TLS configuration you may follow instructions on Running Jira applications over SSL or HTTPS.


When connecting as a client Jira will start the SSL handshake based off the current Java it's using, Java 8 enables TLSv1.1 and TLSv1.2 in client mode and uses TLSv1.2 by default. The initial request from the client (Jira) will go as TLSv1.2 and since TLSv1.2 is backward compatible, if destination responds on TLSv1.1, then they both agree on TLSV1.1 going forward.


You can verify the SSL handshake in Jira logs, on Logging and Profiling please add the package org.apache.http set to DEBUG. You may also enable this through the following startup parameters: 

The information will be written into JIRA Home Directory/log/atlassian-jira.log when a secure connection is stablished.


If you wish to restrict TLS versions used by Jira when connecting as a client, you can set the value of the jdk.tls.disabledAlgorithms parameter in <JAVA_HOME>/lib/security/

The current <JAVA_HOME> is available at Administration > System > System Support > System Info > java.home. More Info:

Alternatively, you may add the following startup properties to achieve these settings:


Last modified on Sep 24, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.