Hi all,
I am trying to use MS SOAP Toolkit 3.0 and VB 6 to talk to a web service that we have written using gSOAP with OpenSSL.
The server is currently configured to use the default demo certificates supplied with openSSL (all ending in .pem extension). In this application, the encryption is the important thing, not the authentication.
However, the MS SoapClient refuses to talk to this service. It seems to me that when the client opens the connection, and the server responds with its certificate, the Client quits without sending the SOAP message and throws an error that says "Connector:WinHTTP reported 'security channel error' or unknown security call back."
If I connected to such a service with Internet Explorer, it would give me a popup and I could click 'yes' to proceed, is there no equivalent property that I can set in the soap client?
What do I have to do to make the SoapClient trust this certificate? I used IE to connect to the web service and imported its certificate as a trusted site so that IE no longer prompts me with the warning. . . how do I get the VB client to do the same?
-- Eric
I am trying to use MS SOAP Toolkit 3.0 and VB 6 to talk to a web service that we have written using gSOAP with OpenSSL.
The server is currently configured to use the default demo certificates supplied with openSSL (all ending in .pem extension). In this application, the encryption is the important thing, not the authentication.
However, the MS SoapClient refuses to talk to this service. It seems to me that when the client opens the connection, and the server responds with its certificate, the Client quits without sending the SOAP message and throws an error that says "Connector:WinHTTP reported 'security channel error' or unknown security call back."
If I connected to such a service with Internet Explorer, it would give me a popup and I could click 'yes' to proceed, is there no equivalent property that I can set in the soap client?
What do I have to do to make the SoapClient trust this certificate? I used IE to connect to the web service and imported its certificate as a trusted site so that IE no longer prompts me with the warning. . . how do I get the VB client to do the same?
-- Eric