Preparing mobile apps for TLS 1.0 deprecation
|Knowledge Article Number||000231452|
In early 2016, Salesforce will disable TLS 1.0 and will begin using TLS 1.1/1.2 exclusively. This change is slated to occur sometime in the February to April 2016 timeframe. Details for this change are publicly available in the following knowledge article:
This change will affect existing users of applications built on certain versions of Mobile SDK. To avoid loss of functionality in your app, apply the following mandatory changes to your app as soon as possible.
After TLS 1.0 is disabled on a Salesforce instance, apps that are not compliant with TLS 1.1 or 1.2 will not be able to connect to that Salesforce instance.
The iOS platform (version 5.0 or later) supports TLS 1.1/1.2 out of the box. No changes are required for Mobile SDK apps built with iOS 5.0 or later. Older apps must upgrade to a supported iOS version.
Unfortunately, some work might be required to ensure that your Android applications don’t break when TLS 1.0 is disabled on a Salesforce instance. We have a fix that enforces TLS 1.1/1.2 on Mobile SDK Android applications:https://github.com/forcedotcom/SalesforceMobileSDK-Android/pull/981. The fix is currently in our ‘unstable’ branch. It will be included in our upcoming Mobile SDK 4.0 release (expected in November/December 2015).
Android Versions Affected
As an application developer, use one of the following options to ensure that your users on KitKat aren’t affected by the change in April.