Greetings,
We are facing a problem with TLS 1.2 protocol, We are using SOAP object class in our application to connect our client web service, now they changed their protocol from TLS 1.0 to TLS 1.2, when our Application (build on pb2017r3 ) is running from Windows 10 it is taking TLS 1.2 protocol automatically, but it is not taking TLS 1.2 protocol while running same application from Windows Server 2012r2.
Also we tried the following registry entries workarounds.
https://www.admin-enclave.com/en/articles/windows/305-enable-tls-1-2-on-windows-2012-r2.html
Please guide how we can solve.
Regards
Antony
Can you guide me, why it is working from Windows 10 ?
Regards
Antony
My guess is that the registry "hack" for W10 will not work on W2012 because that Windows "Server" edition did *not* share the same W10 "kernel" of the O/S until W2016 and higher. If you can, I would try this with W2019 Server and see if that registry hack might work there.
If the newer Windows Server registry hack does not work, it could be something that MS has done in the Windows "server" editions. Its hard to know exactly unless your an MS engineer. The other consideration is that the W10 registry hack may not work in newer versions (ie: W10X). So I would suggest looking at the HTTPClient object class moving forward for TLS 1.2 / 1.3 support.
FYI: https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/236-call-soap-web-services-using-httpclient-object
HTH ... Chris