You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
As part of our quest to better secure Atlassian cloud products, Atlassian will be disabling support for Transport Layer Security (TLS) v1 and v1.1, effective December 1, 2018. We are urging companies using the Atlassian cloud products listed below to upgrade to TLSv1.2 before this date. Please read below to determine if you are affected and, if so, how to start making preparations for the change.
This will affect all HTTPS traffic to Atlassian cloud products, including:
The types of traffic which would be impacted include:
*SSH traffic to bitbucket.org or altssh.bitbucket.org will not be affected by this change.
Many of HTTPS requests to Atlassian cloud products already use the newest version of TLS, v1.2. This includes all recent versions of our supported browsers. However, some requests include a number of remote CI/CD systems, scripts, and programs which interact with our APIs; all of which use older versions of Java, OpenSSL, .NET Framework, RestSharp, NING or Python’s ssl module when negotiating the secured connection to Atlassian cloud products. All of these will be unable to connect once we disable TLSv1 and TLSv1.1.
Please note: Payment processing pages have already moved from TLSv1, to comply with PCI requirements.
We plan to contact some teams and users directly, based on what we find in our logs. However, we recommend that you check to make sure that everything you use to connect to Atlassian's cloud products supports TSLv1.2. This includes (but is not limited to) your browser, Git or Mercurial client, CI/CD system, API clients, and anything else that may be linked to our products.
The following list is an overview of items which may or may not affect you.
Please upgrade anything that is affected before December 1, 2018. The exact details of your upgrade will depend on what you use and how it’s installed. We don’t have enough room here to list all the different combinations, unfortunately, but we hope that the section above will point you in the right direction. We’ll remind everyone as December 1 approaches, but if you discover that you are affected, then you need to start planning now.
Keeping your Atlassian cloud product experience secure is a priority for us. We understand that system upgrades can be complicated, especially on shared systems. We appreciate your support and patience as we disable older versions of TLS in the coming months.
As always, please contact our support team if you need additional information or ask questions in the comments below!
Sr DevOps Engineer, Bitbucket Cloud
San Francisco, California, USA
63 accepted answers