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

Resolved PB SOAP webservice TLS1.2 Support

  1. Issue
0
Votes
Undo
  1. Rajesh Selvam
    Rajesh Selvam
  2. PowerBuilder
  3. Tuesday, 27 February 2018 22:01 PM UTC

Hi,

We are currently using PB 12.1. We consume a soap webservice from external vendor in our app. The vendor is going to disable the support of TLS 1.0 and 1.1 soon.

Is there a way to configure PB to use TLS 1.2 protocol?

We can migrate to PB 2017 if it would support TLS 1.2. But we can't go to R2 release at this time (because of bug #744).

Appreciate any help. Thanks, 

  1. Build
Failed to generate DWSQL.
"Potential" Show stopper for 2017R2 - FIX NEEDED A...
Responses (2)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 1 March 2018 00:14 AM UTC
  2. PowerBuilder
  3. # 1

You would need the external vendor to provide you with a REST version of the web service or create some sort of proxy bridge to wrap the SOAP Web service as a REST Web API.  Alternatively, there may be external SOAP clients supporting TLS 1.2 that you could embed in your app, but that would not be a native/built-in solution so it brings a different set of hassles.

As far as the bug you mentioned, on March 31, 2018 Appeon will be releasing the fix so this should only be a temporary obstacles for you to upgrade.

Comment
Miguel Leeuwee
  1. Miguel Leeuwee
  2. Thursday, 1 March 2018 00:24 AM UTC
Hi Armeen, maybe I'm too fast, but the release date, that is useful information which might be nice to show in the related bugs. The bugs are only saying it will be fixed ASAP and not 31th of March.

  1. Helpful
Rajesh Selvam
  1. Rajesh Selvam
  2. Thursday, 1 March 2018 16:45 PM UTC
Hi, 





Is there a workaround to make PB12.1 to use TLS 1.2? any example you can point me to? any suggestion on non-native soap client?



We will eventually switch it to use REST based web service with R2 version but need to do something in the interim. 

As bug fix release won't be out until Mar 31st and considering time to go through another round of regression testing of our apps, I doubt we would be in with R2 version before vendor stops TLS 1.1 support. 



Help please!! Thanks!

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 27 February 2018 23:57 PM UTC
  2. PowerBuilder
  3. # 2

Hi Rajesh;

  FYI: Sounds like ticket #744 will be fixed in the next EBF for R2.

Yes, R2 supports TLS 1.2 in both the RESTful Client and HTTP Client object classes.

Regards ... Chris

Comment
Bruce Armstrong
  1. Bruce Armstrong
  2. Wednesday, 28 February 2018 17:19 PM UTC
The RESTClient and HTTPClient do support 1.2, but you can't use the first to call a SOAP web service and the second would require a great deal of bare metal coding to do it.

  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.