Refer to SFDC announcement at https://help.salesforce.com/apex/HTViewSolution?urlname=Salesforce-disabling-SSL-3-0-encryption:
Refer to SFDC Knowledge base article for TLS 1.1 compatibility : https://help.salesforce.com/articleView?id=000221207&type=1
Q: What is the change?
A: In November and December 2014 Salesforce disabled SSL 3.0 encryption to prevent it from being used to access the Salesforce platform. Any channels connecting to Salesforce will need to use TLS 1.0 encryption or higher see below for supported encryption protocols. There are three different channels that require encryption to access Salesforce: internet browser, API (inbound) integrations, and call-out (outbound) integrations.
Q: Why did this happen?
A: At Salesforce, trust is our #1 value, and we take the protection of our customers' data very seriously.
On October 15, Google researchers published details on a security vulnerability (CVE-2014-3566) that affects the Secure Socket Layer (SSL) 3.0 encryption protocol, also known as POODLE, which may allow a man-in-the-middle attack to extract data from secure HTTP connections. Although the vulnerability is somewhat difficult to exploit, to further protect customers, we will be disabling SSL 3.0 to fully address this issue.
Q: Which non-SSL 3.0 encryption protocols does Salesforce support?
A: Salesforce currently supports the following encryption protocols:
For inbound requests: TLS 1.0, and TLS 1.2
For outbound requests: TLS 1.0
Q: What should I do if I am experiencing handshake errors?
A: We recommend you test the call-out integration in a Sandbox. If you continue to receive handshake errors in the Sandbox, then log a case via the Help & Training portal.
- Data Services 14.2.
- SFDC adapter.
KBA , EIM-DS , Data Services , Product Enhancement
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.