8

I heard that salesforce would stop the support for SSL 3.0 and will enforce TLS 1.0 and higher. https://help.salesforce.com/apex/HTViewSolution?urlname=Salesforce-disabling-SSL-3-0-encryption

From salesforce, we are making callouts to SAP system and get data from there. What changes should I make to SFDC side as well as on SAP side? Also, what suggestions should I give to tech guys who are on SAP side?

Experts please clarify it is very urgent for us so that we are in a position to tell our client. Experts, any thoughts on this? Please help me out. Thanks

7
  • Is this in regard to the recent SSL3.0 POODLE attack vulnerability?
    – BarCotter
    Commented Nov 3, 2014 at 17:11
  • Yes. Exactly. I have referred this article and getting confused as it explains the solution in a single sentence like this, "....... If a customer uses call-out integrations, then they need to ensure TLS 1.0 encryption or greater is enabled in the integration. " I literally do not understand what we need to do on either end i.e., SFDC side and SAP side. I am making callout from SFDC to SAP and get data from there.
    – Bforce
    Commented Nov 3, 2014 at 17:19
  • Which article are you referring to?
    – BarCotter
    Commented Nov 3, 2014 at 17:22
  • I am sorry . forgot to include the article, please see help.salesforce.com/apex/…
    – Bforce
    Commented Nov 3, 2014 at 17:26
  • You could try disabling SSL in whatever system you use to connect to SF and verify that the connection uses TLS.
    – user6861
    Commented Nov 3, 2014 at 21:47

1 Answer 1

1

All Salesforce sandboxes now have this implemented. Point one of your sandboxes to a test instance of SAP and run your integration test scripts.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .