On December 31, 2020, Playment will no longer support SSL, TLS 1.0 or TLS 1.1 over HTTPS which means older browsers or API clients that do not support TLS 1.2 will no longer work after this date. This includes all URLs and domains owned and operated by Playment, specifically playment.io and playment.in.
This change is in recognition of website security best practices.
We also wanted to give you as much notice as possible in the event your IT team needs to upgrade browsers or make changes to your applications, if required (See “How to Test” below).
You may have heard of these vulnerabilities by some of their better-known names such as Heartbleed, Poodle, Freak and Beast. These vulnerabilities concern the weak encryption of sensitive data transmission over the internet, which may allow unauthorized parties to view the data. All versions of SSL, and versions of TLS before TLS 1.2 have been explicitly identified as no longer being a strong form of encryption because they are vulnerable to many known attacks.
Most browsers have supported TLS for at least the last few years, so end-users are unlikely to be affected by this change. The biggest impact is likely to be felt by API users with very old libraries.
A comprehensive list of browsers and the version supported is available here: https://www.ssllabs.com/ssltest/clients.html
Point your browser, API client, or code to https://tlscheck.playment.io . You should expect to see “Connection OK” (with a 200 response code). If you see that, then you have successfully connected and are all set. If your client throws an SSL, TLS, Connection, or Negotiation error, then you will need to upgrade your language or library in order to remain compatible
If you have code that connects with the Playment API, you must ensure that it will continue to work after December 31, 2020. Each language and library is different, however we’ve identified the popular ones that may be of concern. These languages will need significant changes/upgrades in order to work:
openssl version. Version 1.0.1 in the minimum required.We would be happy to help you ensure compatibility in any way we can. However, please keep in mind that we are not experts in every language or framework and so we aren’t able to test or fix your code for you.
Most browsers have supported TLS 1.2 for several years.The following browsers DO NOT support TLS 1.2 and will no longer work.