Soap Viewer HTTPS

Hi,

Just found out that the Progress SOAP viewer will not work for https. Anyone know of any way I can listen for messages with https?

Thanks in advance,
Paul
 
I dont really understand what you are trying to do. Are you trying to call https based webservice? If yes, you can use certutil to install ssl certificate for Progress to use.
 
Cheers for the util DwinTX.

rusguy.. basically trying to acess a third party webservice over SSL. New to all this so feeling my way.. Got it working via a util called SoapBox so I have confirmed that the web service is functioning ok.

When I try and access the service from Progress, I can connect but when I try an invoke a method, I get the following:

Error receiving Web Service Response: Fatal error: csnet read operation failed (WinSock reported error=0) (11773).

I have imported the cert into Progress that the third-party send out to me. I have also browsed to the webservice and exported the certificate there and imported to Progress but still getting the errors... Just trying now to trace what is happening.
 
This error can mean different things. Are you behind a firewall? It could be that the firewall isn’t assembling the packets right. Are you using a proxy? If yes, you need to specify your proxy at a client startup with –proxyhost/-proxyport parameters.
It could be a problem with a certificate – but since you said that you could connect to it, than probably it is not an issue. And also it could be a problem with WSDL itself, like bad method name or a bad address in there somewhere – some of these could be fixed with parameters in the connect method.
 
This error can mean different things. Are you behind a firewall? It could be that the firewall isn’t assembling the packets right. Are you using a proxy? If yes, you need to specify your proxy at a client startup with –proxyhost/-proxyport parameters.
It could be a problem with a certificate – but since you said that you could connect to it, than probably it is not an issue. And also it could be a problem with WSDL itself, like bad method name or a bad address in there somewhere – some of these could be fixed with parameters in the connect method.

Cheers rusguy. I think I have ruled out most of these issues as I've managed to connect and invoke a method on the web service by using a utility called SOAPbox from the same PC so that would seem to rule out any firewall/cert issues. Query seems to be going out but no response seems to be coming back in so I am thinking it could be to do with the trusted certificate.. it's not very apparent which cert Progress is using.
 
I think I have ruled out most of these issues as I've managed to connect and invoke a method on the web service by using a utility called SOAPbox from the same PC so that would seem to rule out any firewall/cert issues.
Not really - Progress doesnt use built in windows cert repository and it uses its own means to connect to the outside world. So, any utility you use outside Progress just shows you that you can connect to the destination and nothing else. But it does rule out any firewall issue.

Query seems to be going out but no response seems to be coming back in
Connect method doesnt really connect to the webservice, it only does it when you run a method on that server. So, if it doesnt work it means it couldnt connect. You could put a network sniffer in between Progress client and a web server to see what Progress sends/receives.

so I am thinking it could be to do with the trusted certificate.. it's not very apparent which cert Progress is using.
Its simple - it uses its own certificate repository, that has nothing to do with IE's one.
 
Not really - Progress doesnt use built in windows cert repository and it uses its own means to connect to the outside world. So, any utility you use outside Progress just shows you that you can connect to the destination and nothing else. But it does rule out any firewall issue.


Connect method doesnt really connect to the webservice, it only does it when you run a method on that server. So, if it doesnt work it means it couldnt connect. You could put a network sniffer in between Progress client and a web server to see what Progress sends/receives.


Its simple - it uses its own certificate repository, that has nothing to do with IE's one.

rusguy, thanks again for the response.

After a couple of days of pulling my hair out, I finally got hold of someone in Progress Support who could help. Turns out the problem is that Progress does not currently support mutual authentication when making a web service call from the 4GL. They had mentioned that something called stunnel could be used but isn't supported.
 
nice one, another language limitation :mad:

In this case you would need to write a wrapper in another language like java or .net to talk to a web service and then return data back to Progress.
 
Back
Top