FYI, I have now cracked this problem. I had something of an epiphany last night >-)
The problem lies with Bill Gates! The default .keystore is created in the current Windows users home directory. The path to this directory has a white space in it, which the JVM does not like. If you try and use your own keystore, Tomcat does not like it. The trick is to create the default .keystore file, import your client certificate and then copyt the .keystore to another location with no white space in the path. You then specify the location of the .keystore and the password for the store on the line in the catalina.bat file that starts Tomcat. Obvious!!!! Of course the better alternative is to develop and host using Linux or Solaris (but my client won't do that!!!) Later .... email: [EMAIL PROTECTED] http://www.mojoco.biz/ -----Original Message----- From: Justin Brister [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 6:04 PM To: '[EMAIL PROTECTED]' Subject: Hosting SSL clients within Tomcat I am trying to open a connection to an SSL server hosting WebServices. I am using the Glue libraries to abstract away all the nasty Web Service stuff, and my WebService client is implemented as a Servlet. I have imported the SSL certificate into my .keystore If I run my client code as a stand-alone app. it works OK If I use the keystore to configure SSL connections for Tomcat it is fine However, if I run my client code from within a servlet, Tomcat complains that either the trust store has been tampered with or the password is invalid. Does anyone have any idea how I can configure Tomcat to find the truststore and load the appropriate certificates for use by my SSL client? Thanks, J --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
