About this time last year, we announced the end of support for TLS 1.0 for libraries being hosted by Adobe. In the same vein, we want you to know that in the early part of April 2020, DTM and Launch will end support for TLS 1.1. TLS 1.2 will be the minimum allowed version. We will update this post with the exact date when it moves closer and we determine what it is.
As before, this is a security requirement coordinated across many Experience Cloud solutions so that they can be in compliance with certain data security standards required for companies who do credit card processing.
Effectively, this means that browsers that do not support TLS 1.2 and above will no longer be allowed to retrieve a hosted library over an HTTPS connection. If you are using HTTPS to load your DTM or Launch library, then those browsers will no longer be able to retrieve and execute that library.
Browsers that support TLS 1.2 and above - and will continue to function as they do today - are:
Chrome 30 and up (current version: 79)
Safari 7 and up (current version: 13)
Firefox 27 and up (current version: 72)
Internet Explorer 11
Any version of Microsoft Edge
iOS Safari 5 and up (current version: 13.2)
Here are a few other ways of looking at it:
June of 2014 was the last time that any browser maker anywhere released a version that doesn’t support TLS 1.2
The number of browsers that support TLS 1.2, but not TLS 1.1 (the ones affected by this change) make up about 0.04% of global traffic
More details about browser support for TLS 1.2 are available in a number of places, but this is a good starting point.
As before, if you require that your DTM or Launch libraries load over HTTPS in a browser that only supports up to TLS 1.1, you will need to begin hosting your own library on servers that are configured to still support TLS 1.1.
We regret any inconvenience this causes for you, however, we take security and compliance very seriously and feel that the benefits of this change outweigh the costs.