ATTENTION: Action Required for .NET Integrations by March 2017

Follow

.NET-based integrations that send requests to Salesforce and are not enabled with TLS 1.1 and/or TLS 1.2 will cease to function after the disablement of TLS 1.0 for all instances by March 2017*.

* TLS 1.0 disablement is scheduled for March 4, 2017 at 9:30 a.m. PST (17:30 UTC) for all production orgs.

As an admin for a Salesforce org that uses .NET-based integrations to send requests to Salesforce, we strongly encourage you to enable TLS 1.1 and/or TLS 1.2 in those integrations well in advance of March 2017, as such changes require planning and testing.

What should I know?
.NET-based Salesforce integrations are interfaces or applications–including mobile apps and desktop clients–that are separate from Salesforce, but use Salesforce data. The disablement of TLS 1.0 for all instances by March 2017 will disrupt such applications if they do not support TLS 1.1 and/or TLS 1.2.

How do I get started?
We recommend you enable TLS 1.1 and/or TLS 1.2 in all of your .NET integrations as soon as possible. Customers should work with their integration partners to assess and update their .NET integrations. To identify your .NET integrations that still rely on TLS 1.0 to connect to Salesforce, view the TLS 1.0 logins that have a Browser field or column that starts with .NET from the Login History.

Additionally, see the .NET compatibility requirements in the Salesforce disabling TLS 1.0 article for detailed guidance.

How can I get for more information?
Review the Salesforce disabling TLS 1.0 article and post your questions to theInfrastructure Success Community group. Follow the discussions in the “BeTLSReady” and “TLS 1.0 Disablement” Chatter topics within the Success Community.

For additional questions, open a case with Support via the Help & Training portal.

Have more questions? Submit a request

Comments

Powered by Zendesk