Re^3: SOAP and class1 cert

It's been a while since I had to troubleshoot a problem like this, but in the past, I think I fired up a browser on the soap client, imported the cert, and tried to access the remote soap server that way. As I remember, this helped me track down cert issues independent of the soap layers. Don't know if it will help in your case. Good luck.

Comment on Re^3: SOAP and class1 cert

Replies are listed 'Best First'.
Re^4: SOAP and class1 cert by Hammy (Scribe) on Aug 24, 2005 at 20:51 UTC
You peaked my interest a little. How could I use my browser to access the remote SOAP service?	[reply]
Re^5: SOAP and class1 cert by cbrandtbuffalo (Deacon) on Aug 25, 2005 at 19:51 UTC
Well, I used it as a sort of crude debugging tool. If the soap resource is running through a server, you can try to hit the server. The response may not make any sense to the browser, but if you're actually getting to the resource that means the cert negotiation worked. If you can get that far with the browser but not the soap, it means the cert is OK, but the soap isn't using it right.	[reply]
Re^4: SOAP and class1 cert by Hammy (Scribe) on Aug 25, 2005 at 15:59 UTC
Problem solved. I used openssl on my APACHE box to translate the pfx file to a pem file. Once doing that I still ran into a few problems until I used an option to remove the password from the key. Once doing that, all worked like a charm.	[reply]