Extended Deadline for TLS 1.0 Disablement in Communities

On July 22, 2017, Salesforce is disabling support for TLS 1.0 (Transport Layer Security protocol) for all orgs in production. To give admins more time to prepare community users, the TLS 1.0 disablement deadline for Salesforce Communities has been extended to March 2018. The extended March 2018 deadline applies to both Lightning and Visualforce communities.
Note

Note

Partner portals, customer portals, and Force.com and Site.com sites are still subject to the July 2017 deadline as previously announced.

As a result of this change, browser access, inbound API integrations, and call-out integrations are required to be compliant with TLS 1.1 or above. We encourage you to inform and educate your community users this transition. All licensed and unlicensed community users (guest users) must upgrade to browsers that are compliant with TLS 1.1 or above.

To prepare for this change ahead of time:
  • Add appropriate messaging to your communities to inform your users about TLS 1.0 disablement. Educate both licensed and guest users about browser requirements for TLS version compatibility.
  • Encourage users to check their browsers for compatibility with our test site. If their browser is compliant, the web site displays a “Test passed” message.
  • Ensure that the TLS 1.1 or above is enabled for your API integrations.

If you’d like to turn off TLS 1.0 for communities along with your Salesforce org or ahead of the March 2018 deadline, we’ve got you covered! In Setup, type Critical Update in the Quick Find search box and select Critical Updates. Activate the critical update that disables TLS 1.0 support for Salesforce Communities. You can deactivate this critical update to restore support for TLS 1.0 connections.

For detailed information TLS 1.0 disablement, see this knowledge article.