Was TLS 1.0 still being supported by JIRA Cloud after Dec 1 2018?

Fabrizio Ferri-Benedetti

Hi there,

We've been successfully running a PowerShell script to get data via our JIRA Cloud REST API. Then, a few days ago, we got this error:

Invoke-RestMethod : The request was aborted: Could not create SSL/TLS secure channel.

We didn't know about TLS 1.0 being phased out on Dec 1, 2018 for all Atlassian products, As PowerShell uses TLS 1.0 by default, we fixed the issue by adding this line to the script:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls -bor [Net.SecurityProtocolType]::Tls11 -bor [Net.SecurityProtocolType]::Tls12

But we still don't understand why we could run our requests over TLS 1.0 for months. Has the TLS 1.0 cutoff been rolled out in waves?

Thanks,
F.

 

Andy Heinzer

Hi Fabrizio,

I understand you have some concerns in regards to whether or not Jira Cloud was still supporting TLS 1.0 after that announcement date.  One of the original announcements about this change was in https://community.atlassian.com/t5/Jira-articles/Deprecating-TLSv1-and-TLSv1-1-for-Atlassian-Cloud-Products/ba-p/857357  Back in July 31, 2018.

While the planned effective date in that page was December 1, 2018, you can see in the latest Jira Cloud blog updates

https://confluence.atlassian.com/cloud/blog/2019/07/atlassian-cloud-changes-jul-1-to-jul-8-2019

... after consultation internally and with customers, we have allowed a silent/soft grace period of 6 months to allow customers additional time to update the necessary tools and systems. This grace period has now expired. 

So in short, yes it was still possible to use after the planned effective date, even though this had been deprecated.

I hope this helps to clarify the situation.  Please let me know if you have any additional concerns here.

Andy