Buzz: TLS 1.1 Deprecation Notice (2020-08-13)Follow
Agilix will be disabling support for TLS 1.1 on August 13, 2020, across the Buzz platform, including the Buzz API. This change will not impact any of the supported browsers as each of these support TLS 1.2 or greater.
Why is Agilix disabling TLS 1.1?
We are disabling TLS 1.1 to ensure that the Buzz platform is providing our learners, teachers, and partners with safe and secure protocols for all of our applications. As of March 2020, all major browsers require a minimum of TLS 1.2 and many networking services require TLS 1.2 or greater.
Do I need to make any changes?
If you use Buzz exclusively through a supported browser, no, you do not need to make any changes.
If you are not using a supported browser, you will need to check to see if your browser supports TLS 1.2 or a greater version. If it does not, then you will need to begin using a supported browser.
Buzz API clients
Customers who have written their own integration (e.g., rostering, reporting tools) and are using clients that do not support TLS 1.2 and above will no longer be able to successfully connect to the Buzz API. Customers must ensure that they are using an HTTP client library which supports TLS 1.2 before the deprecation date.
We encourage each customer that utilizes the Buzz API to ensure that they are prepared for the deprecation date.
You can use the following API to easily test the library you are using for Buzz API connections to ensure it supports TLS 1.2 or greater.
The HTTP response will contain a
tls_version value that contains the highest version of TLS that is supported by the client.