Resolving error "UNSUPPORTED_CLIENT: TLS 1.0 has been disabled in this organization...."

created

UPDATE: As of June 15, 2016, TLS 1.1 is supported across the entire Soapbox server architecture. This error should no longer occur and you can activate the "Require TLS 1.1 or higher for HTTPS connections" Salesforce update. The following article is retained only for historical reference.

Resolving the following error: "UNSUPPORTED_CLIENT: TLS 1.0 has been disabled in this organization.  Please Use TLS 1.1 or higher when connecting to Salesforce using https."

Salesforce.com currently allows the disabling of TLSv1, a security protocol used by web services to talk to each other. If this version of TLS is disabled in your Salesforce service, Soapbox will not be able to function properly in some cases, since some of the Soapbox servers still require the use of TLSv1.

We are in the process of updating our server architecture and will notify the community over the Soapbox  updates forum when that is done.  You can subscribe to that here: http://support.picnet.net/forums/60255-Soapbox-2-Soapbox-Engage-Updates-and-Alerts.

You'll be able to see if this is causing an error in Soapbox by going to Monitor > Jobs > Apex Jobs and seeing if there is an error that includes the following message:

"First error: Server chose TLSv1, but that protocol version is not enabled or not supported by the client."

If so, this means that TLSv1 was deactivated in your Salesforce account. Salesforce will not be forcing the deactivation of TLSv1 until March 2017, so if you want, you can easily re-enable TLSv1 by doing the following.

  • Go to Build > Critical Updates
  • Under the Update Name column, look for "Require TLS 1.1 or higher for HTTPS connections"
  • For the row that has "Require TLS 1.1 or higher for HTTPS connections", click the "Deactivate" link

If you want to reactivate this update in the future, just click the "Activate" link.

Have more questions? Submit a request
Article is closed for comments.