RE: WSDL2Java and SSL

[Tootell, James]

Chris,       Wow, that is very odd.       As I understand it, TCPMON acts as a proxy and is supposed to just pass along the messages sent to it without affecting them.  I'm wondering if this is an encoding issue with the certificate hash.  I bet the JRE uses a character set that the server likes and maybe TCPMON is converting your Axis message to a character set that the server likes but Axis itself is sending things out using a character set that corrupts the certificate hash.        This is really low-level stuff though and outside my expertise so hopefully others have some insight.  If I were you, I'd try to get some fresh input by posting a new thread listing all the latest lessons-learned.   Good luck,   Jim From: Chris Hall [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 28, 2005 2:38 PM To: axis-user@ws.apache.org Subject: RE: WSDL2Java and SSL Jim,   I ran TCPMON to monitor TCP packets and the strangest thing happened.  With TCPMON sitting between my Axis stub and the server I get a good success message from the server.  When the Axis stub connects directly to the server I get the same cert authorization failed error I have been seeing.   Both the Axis stub and TCPMON are running on the same machine, which was my first though for an explanation.  Now I’m mystified as to what is going on.   Thanks, --Chris