Skip to Content
author's profile photo Former Member
Former Member

12.6 PB Web Service Client .NET ENGINE TLS 1.0 PROBLEM

Hello we are developing a client for cosumming a WS.

The problem is that our firewall, ZScaler does not allow communications over TLS 1.0 (deprecated since 30th June 2016) , so we always get a sopa Exception because of emptty response(zScaler does not send the content to us).

The ws client is a .NET engine client.

Anybody knos how to solve this? Is thaere any possibility for working with the sopaconnection object using tls1.2?

Regards

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 25, 2016 at 04:07 PM

    Hi Juan;

    Until Appeon can address PB's Web services deficiencies, I wonder if using a 3rd party control or a callable Java Class to broker the WS interaction might be the way to proceed?

    FYI:. https://www.example-code.com/powerbuilder/http.asp

    Regards ... Chris

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi, thanks a lot Chris...

      We have already tested with a.jar class and also with activeX. Both are good solutions and Works fine.

      For us is more "comfortable" to work with a PB client, and now we are trying to get permission of our company to use soap 1.0 through Zscaler at least for the domain of the WS.

      In order to ensuere a long lifwe solution, I asked if there is prevssion from Appeon of implementing TLS1.2 versión in nexts builds/versión.

      Thanks a lot again for your help, Chirs

  • Posted on Jul 26, 2016 at 08:31 AM

    Hi Juan,

    we had also the requirement to use a webservice with TLS 1.2.

    Our Solution: We built a .NET assembly to use the webservice using .NET and use that via COM. You must use .NET 4.5 Framework because TLS 1.2 is not implemented in previous versions.

    You can use WSEWSDL3.EXE (part of Windows SDK 7.1) to build a class for WSDL. You have to extend it to set the security protocol:

    System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;

    For more information about build and use a COM object for an assembly look for Bruce Armstrongs detailed description: Using .NET Assemblies with PowerBuilder

    HTH,

    René

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.