Update, 14/02/2017: Salesforce has recently decided to extend the date from which the security updates discussed in this article will take effect. The TLS 1.0 disablement deadline will now fall on July 22, 2017 (except for sandboxes, for which the extended disablement date is July 15, 2017). For more information, a full update can be found in this alert, published this week by Salesforce.
Salesforce will no longer support a version of a common security protocol known as TLS v1.0. Those accessing the Salesforce platform will consequently be required to use TLS v1.1 at a minimum, which will have an impact on business users of Salesforce mobile apps, as well as partners delivering apps for their Salesforce clients. This article explains what this means for MobileCaddy customers, and provides more detail for anyone not using MobileCaddy for their Salesforce mobile apps.
What you need to know with MobileCaddy
One of the key benefits of using MobileCaddy to deliver mobile apps within a business is an environment manager which is built-in as an inherent part of the product. This is a system that not only monitors changes to the environment all our apps operate within, but allows us to easily repair problems and deploy fixes as well, ensuring confidence and trust in the apps’ performance are maintained at all times.