Today, in line with data encryption best practices, we're deprecating Iterable's API support for incoming calls that rely on Transport Layer Security (TLS) 1.0 and 1.1. We'll completely disable support for TLS 1.0 and 1.1 on October 22, 2021. Starting on that day, API calls that do not support TLS 1.2 will fail.
On affected devices and servers that are not updated to support TLS 1.2 before October 22, 2021, this change will impact any function that relies on Iterable's API. For example, apps running on mobile devices that don't support TLS 1.2 will be unable to track events in Iterable or receive in-app messages (regardless of whether your app uses one of Iterable's mobile SDKs or calls Iterable's API directly).
The vast majority of Iterable's customers will be unaffected by this change. However, a small amount of API traffic (.04%) is at risk.
In particular, some mobile devices running Android 4.4 or lower may be affected by this change. Some of these devices may already have TLS 1.2 enabled by default, and they will continue to work as expected. Others may not have TLS 1.2 enabled by default, and they will be unable to communicate with Iterable. Code fixes suggested in Android's documentation may help some of these devices, but not all.
To understand and mitigate any concerns related to this change:
- Determine how many of your users are running Android 4.4 or lower, and work with your developers to decide whether or not to explore the code fixes suggested in Android's documentation.
- Ensure that calls from your server to Iterable's API support TLS 1.2.
(This is not an exhaustive list.)
We'll send an email notification on October 22, 2021, when we disable support for TLS 1.0 and 1.1.
If you have questions about this change, talk to your customer success manager.