Support for TLS 1.0 and TLS 1.1 will be withdrawn from API Connect offerings for IBM Cloud on March 1st, 2018.

This is occurring in coordination with the withdrawal of TLS 1.0 and 1.1 support for many other IBM Cloud offerings on the same date. General information, including a list of other affected products and services, is available here:
IBM Cloud Docs / Troubleshooting – Withdrawal of support for TLS 1.0 and 1.1

Which offerings does this affect?

  • API Connect for IBM Cloud
  • API Connect for IBM Cloud Reserved

How can I make sure I will not be impacted?

You will need to inform your API consumers (subscribers) that, after the removal of support for the older versions of TLS, they will no longer be able to call your APIs from client software which does not support the newer TLS versions. They must ensure that they are already using software which supports TLS 1.2, or upgrade to versions which support TLS 1.2 .

Is there a way I can keep using TLS 1.0 or 1.1 after support is withdrawn?


What if I have a question, concern or problem?

Use “Join The Discussion” below.

2 comments on"Withdrawal of support for TLS 1.0 and 1.1"

  1. This isn’t very practical. We still have legacy systems that only support TLS 1.1. How do you plan to cater for that?

  2. You may be able to use an intermediary to resolve legacy issues. A proxy with https inspection which allows TLS1.0 connections on the client-side but makes TLS 1.2 connections upstream could solve this for you. A number of our WinGate customers have recently been dealing with this issue, it’s not always possible to update legacy systems.

Join The Discussion

Your email address will not be published. Required fields are marked *