TLS 1.1 Problem with WebService

[Filippe]

Hi everybody!


We're having trouble integrating with salesforce using a webservice!
The Web server is using [b]TLS 1.1[/b], but it still gives me an error message like below:


11/22/16@23:04:30.315: [SOAP Client 0000000000fb5f90] SOAP Fault, faultcode: '"urn:fault.enterprise.soap.sforce.com":UNSUPPORTED_CLIENT', faultstring: 'UNSUPPORTED_CLIENT: TLS 1.0 Has been disabled in this organization. Use TLS 1.1 or later when connecting to Salesforce using https.', faultsubcode '"urn:fault.enterprise.soap.sforce.com":UNSUPPORTED_CLIENT', faultdetail '<sf:UnexpectedErrorFault><sf:exceptionCode>UNSUPPORTED_CLIENT</sf:exceptionCode><sf:exceptionMessage>TLS 1.0 Has been disabled in this organization. Use TLS 1.1 or later when connecting to Salesforce using https.</sf:exceptionMessage><sf:upgradeURL>https://cs21.salesforce.com/secur/weakhttps.jsp?l=29</sf:upgradeURL><sf:upgradeMessage>
Stronger security is required</sf:upgradeMessage></sf:UnexpectedErrorFault>'
11/22/16@23:04:30.315: [SOAP Handler 0000000000fb5ee0] Ref 3. Maximum number of attempts (2) to contact Web Service reached

Looks like we are using a TLSV1.0
It's funny because when we do the tests with restClient, the requests are received with TLS 1.1! And it works perfectly!

Did this error happen to anyone?

we are using a Windows 2008
URS 81.400.25


Thanks

[cavagnaro]

URS I think only works with TLS 1.0
Check the reference guide

Enviado de meu E6633 usando Tapatalk

[terry]

URS itself has no much control over that really - TLS support is done with Genesys security package and with by OS of course.
Would propose to check version of security package you using and Windows settings/registry in regards of which TLS is used (if it is Windows of course).   

[Raja Sekhar]

Hi,

We are even Facing the Same Protocol compatibility issue while consuming Sales force web services.

Any Suggestions?

How is this Fixed?

[terry]

From msdn web site:
"TLS 1.1 & TLS 1.2 are enabled by default on post Windows 8.1 releases. Prior to that they were disabled by default. So the administrators have to enable the settings manually via the registry. Refer this article on how to enable this protocols via registry: https://support.microsoft.com/en-us/kb/187498"

Would propose to set up all latest patches on windows and do something like for example:
[quote]In my test environment and windows server 2008 R2 SP1  I had similar issues until I did the following:
1. created key "TLS 1.1" under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols
    so have the following key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1
2. create "Client" and "Server" keys there
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client
3. under Client and Server keys I created two DWORD(32 bit) values: one with name "DisabledByDefault" with hex value 0 and another with name "Enabled"and value 1 in hex.
After this changes I see that httpbridge is able to use TLS 1.1.[/quote]

[Raja Sekhar]

Thank you so much Terry...

It works Perfectly....

Than you very much....

[vmc]

Is this all that's required for TLS 1.2 as well?  No URS/IRD upgrade from 8.1.3 -  8.1.4 required?

Sent from my Redmi Note 3 using Tapatalk

[terry]

No upgrade required.

[vmc]

Perfect that's what I found too and had a disagreement with a Genesys support engineer over it.  Contradicts their own information, but it works.

Sent from my Redmi Note 3 using Tapatalk