Problem in accessing the web service through https

[Former Member]

We have web service written in java that can be successfully invoked through normal http using EasySoap. But having problem invoking through https.

Getting this error.

It is working well with SoapUI through https.

We have PB 11.5 professional and we are testing web services with PowerBuilder 12.5.2 Build 5006 Evaluation software.

Please help.

Thanks,

John

[Former Member]

Hi John;

1) Did you use the .NET versdion of the SOAP Connection class?

2) Did you set the Client certificate via the SetClientCertificateFile method?

3) Did you use the SetOptions method to set the UserID and Password?

4) Did you use the Authentication Mode properly?

FYI:  http://msdn.microsoft.com/en-us/library/aa833874(VS.80).aspx

HTH

Regards ... Chris

[Former Member]

Hi Chris,

I am using the EasySoap in PB Classic.

I tried using "Use .Net Engine" in the Proxy wizard and getting "Cannot access the WSDL or the WSDL file is invalid". That same wsdl file worked very well with EasySoap.

The web service is running under tomcat in linux not in IIS.

Thanks,

John

[Former Member]

Hi John;

  It should not matter what application server hosts the Web Service. The key is that it uses standard data types as input and the same ANSI standard data type when returning any result set.

  Can you post the WSDL?

Thanks ... Chris

[Former Member]

Here is the wsdl.

https://efile.taxtimeusa.com:8444/tt-ws/efile?wsdl

Thanks,

John

[Former Member]

PB12.6 Classic had no problem with this WSDL.

[former_member190719]

FWIW, the WSDL is not the issue.  Nor are the data types involved.  At least not yet.

The issue is that the client is having trouble establishing an SSL connection to the server hosting the service.  You might want to try using Fiddler or Charles to monitor the service call and see what is going wrong in the SSL connection attempt.

Also, PowerBuilder uses OpenSSL libraries to make SSL connections.  It's a widely used set of libraries, and you may find that you have several on your machine.   You might want to check to make sure that there is only one (the latest) that all of the applications see.  If PowerBuilder is picking up an older version of OpenSSL than it's own, it might explain the issue with the SSL connection.

[Former Member]

Hi John;

  I had no issues with the WSDL and was able to build a Web Service DataWindow that interacted with the WS OK.

Note: I used PB 12.1 Classic for this test.

HTH

Regards ... Chris

[Former Member]

Thanks Paul. I downloaded PB12.6 classic and able to connect using ".Net Engine".

Thanks,

John

[Former Member]

Hi Bruce,

You mentioned...

"Also, PowerBuilder uses OpenSSL libraries to make SSL connections.  It's a widely used set of libraries, and you may find that you have several on your machine. "

Could you tell me what are the file names and which folder i need to look for.

Thanks,

John

[Former Member]

Hi Chris,

Did you use "Easy Soap" or ".Net Engine"?

I was able to connect with PB 12.6 with ".Net Engine".

Thanks,

John

[Former Member]

Hi John;

  FYI: The WS DW uses the .NET engine by default.  

Regards ... Chris

[former_member190719]

Could you tell me what are the file names and which folder i need to look for.

The files are libeay32.dll and ssleay32.dll

You need to search your entire hard drive.  That's the issue.  There are often several on your machine, as the libraries are quite highly used.

[Former Member]

I'm pretty sure that support for HTTPS web services calls is not available in PB Classic.  You may need to use PB.Net and explore its support for WCF web service calls.

-Paul Horan-

[Former Member]

Hi Paul,

Our application is written in PB Classic and we do not want to migrate to PB.Net now at this moment.

Thanks,

John

[Former Member]

No - you don't have to migrate your entire app to PB.Net.

has more experience here (and I haven't tried this myself), but I think you can use PB.Net to "wrap" the call to the secure web service, and deploy it as a .Net assembly.  Your PB Classic app would instantiate your PB.Net assembly as a COM-callable wrapper.

In PB.Net, create a new .Net assembly.  Add an custom non-visual object, and add a WCF client proxy project that invokes your web service. 

-Paul-