1. Jeffrey Alonzo
  2. PowerBuilder
  3. Wednesday, 13 March 2019 03:38 AM UTC

Hi,

We have just upgraded our applications to PowerBuilder 2017.  We are consuming web services from our PowerBuilder applications, and the web services we consume require TLS versions 1.1 and above (TLSv1.0 has been shut off).  Can you please provide the steps required in regards to PowerBuilder code/configuration/etc. that will allow our PB 2017 applications to communicate using TLSv1.1 and above, as well as provide us with an Appeon contact we can work with to address this issue?

Thanks,

 

Jeff

 

Accepted Answer
Jeffrey Alonzo Accepted Answer Pending Moderation
  1. Wednesday, 13 March 2019 18:21 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Chris,

 

Thank you for your reply.  There was a response we received from Appeon was that only TLSv1.1 is supported via SOAP web service calls, and TLSv1.2 is only available for REST services.  Is this correct, and if so, do you know if Appeon will be providing an upgrade anytime soon to support TLSv1.2 for consuming SOAP web services?  Lastly, are there any windows registry settings that need to be set to support the TLSv1.1 and/or TLSv1.2 calls when using the HTTPClient object?

 

Thanks,

 

Jeff

Comment
  1. Armeen Mazda @Appeon
  2. Wednesday, 13 March 2019 19:11 PM UTC
The response provided was not totally accurate. There are 3 clients that PowerBuilder has... HTTP Client, SOAP Client, and REST Client. The SOAP Client is an obsolete feature that is not being enhanced. The HTTP Client and REST Client support TLS 1.2. The article Chris provided you explains how to leverage the HTTP Client to make a SOAP call.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 14 March 2019 17:34 PM UTC
  2. PowerBuilder
  3. # 1

Hi Jeff;

  Actually, PB's .Net based SOAP feature only supports TLS 1.0 because this feature was originally developed under .Net 2.0 (PB 11.5 time frame). However, there is a registry hack that has worked for some people to allow PB SOAP (.Net variety that is) to use TLS 1.1/1.2. I do not know if this still works in W10, but here are the values for you to try if you are interested ...

32Bit Version:
  [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001

64Bit Version:
  [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001

 

For the "long term" though, the HTTPClient object class would be the best supported way forward by Appeon.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Jeffrey Alonzo Accepted Answer Pending Moderation
  1. Wednesday, 13 March 2019 19:14 PM UTC
  2. PowerBuilder
  3. # 2

Thank you so much for replying Armeen and Chris!

Comment
  1. Armeen Mazda @Appeon
  2. Wednesday, 13 March 2019 20:08 PM UTC
You're welcome, and thanks for marking the correct answer.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 13 March 2019 15:48 PM UTC
  2. PowerBuilder
  3. # 3

Hi Jeff;

  Neither the Web Service DataWindow feature nor the SOAP based Web Service feature of PB2017 support the newer TLS protocols. In order to use TLS 1.1/1.2, you would need to use the new Appeon PB HTTPClient object class. Unfortunately, the XML being returned is not automatically parsed by the HTTPClient - like in the WS DWO for example. So you would  now have to use the PB based PBDOM feature for that.

FYI: https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/236-call-soap-web-services-using-httpclient-object

HTH

Regards ... Chris

Comment
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Wednesday, 13 March 2019 10:25 AM UTC
  2. PowerBuilder
  3. # 4

What method exactly in PowerBuilder are you using to communicate with the web service?

What version/build of PB 2017?

Comment
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.