Archived: Developers Using TfL’s Open Data Feeds – Update

This is an update to the previous post I published on Wednesday 21 December 2016, letting developers know that they need to update to a newer version of TLS.

We've rolled back our change, giving open data users extra time to update their tooling to support modern TLS versions (1.2 and 1.3)
Update: Open data users should aim to update their tooling to support modern TLS versions (1.2 and 1.3) by Wednesday 25 January


On Tuesday 20 December 2016 at 14.40, we deprecated support for older cypher suites such as SSLv3, TLS 1.0 & 1.1, which we ultimately had to roll back that the same day.

This was because there were some reported issues from certain open data users who were using legacy tools that did not support newer versions of TLS (1.2 & 1.3). These tools included older versions of Java SDK.

As a result of this roll back, service was restored to allow affected developers to consume our API and to give them time to update their tooling to support modern TLS versions.

We originally aimed to reinstate the change again on Friday 6th January 2017, but we have had push this back. We are now aiming to implement this change on Wednesday 25 January 2017.

You can test against our new configuration here: https://api-ssl.tfl.gov.uk

Details on supported cypher suites and related toolsets & browsers can be found at https://www.ssllabs.com/ssltest/analyze.html?d=api-ssl.tfl.gov.uk&s=104.16.26.236&latest

We’ll post another notification on Tuesday 24 January 2017 detailing specific timings.