• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • TLS 1.2 taking from, Windows 10 but not taking from Windowserver 12

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved TLS 1.2 taking from, Windows 10 but not taking from Windowserver 12

  1. Advice
0
Votes
Undo
  1. NMC PowerBuilder
    NMC PowerBuilder
  2. PowerBuilder
  3. Wednesday, 12 February 2020 11:26 AM UTC

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://support.microsoft.com/en-ae/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi

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

 

 

 

 

 

Information Required [ Appeon PowerBuilder 2019 Da...
Connecting to Azure DB
Responses (2)
Kevin Ridley
Kevin Ridley Accepted Answer Pending Moderation
  1. Wednesday, 12 February 2020 17:12 PM UTC
  2. PowerBuilder
  3. # 1

Try this:

https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 12 February 2020 11:31 AM UTC
  2. PowerBuilder
  3. # 2

Hi Anthony;

   With the latest PowerBuilder releases, you can use the new HTTPClient to converse with your SOAP webservices via TLS 1.2.

Regards... Chris

Comment
NMC PowerBuilder
  1. NMC PowerBuilder
  2. Wednesday, 12 February 2020 12:39 PM UTC
Hi Chris,

Can you guide me, why it is working from Windows 10 ?

Regards

Antony

  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 12 February 2020 17:28 PM UTC
On Windows 10 you must not be using TLS 1.2. The old SOAP clients never supported TLS 1.2. The HTTPClient is the replacement. In the near future it will also support TLS 1.3.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 12 February 2020 18:02 PM UTC
Hi Anthony;

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
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.