the keystorePass parameter handling in Tomcat in any way.
So why does changeit work but some other password doesn't?
Well, go figure.
Samuli
From: Samuli Seppänen [mailto:[EMAIL PROTECTED] Subject:
Re: Tomcat 5.5 and SSL connector: keystore was tampered with [SOLVED]
I suppose this Tomcat home
From: Samuli Seppänen [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat 5.5 and SSL connector: keystore was
tampered with [SOLVED]
Tomcat SSL Connector entries accept the following parameters:
- keystorePass (password for the JKS (Java keystore)
- keypass (password for the key inside the JKS
I had no problems running with a password other than changeit on any of
5.5.23, 5.5.25, and various 6.0.x levels. As long as the keystore is built with both
passwords the same, everything functions as documented.
Take a look at Troubleshooting section in
http://tomcat.apache.org/tomcat-5.5-du
Update on this thing Tomcat+SSL+keystore thing:
I dug into the Tomcat 5.5.25 source code to see what's really going on.
Here's what I found - hopefully it's useful to someone.
Tomcat SSL Connector entries accept the following parameters:
- keystorePass (password for the JKS (Java keystore)
-
Some additional info:
Debian Etch w/o system-wide Java installation
These are included in the Funambol sync server bundle (6.5.12):
Java Runtime environment 1.5.0
Tomcat 5.5.20
First of all, instead of recipes, I'd prefer to be pointed at
information on how to debug this problem. I'm not a
Hi!
I migrated from Tomcat 5.0 to Tomcat 5.5. I had SSL working in Tomcat
5.0 with both a self-created certificate and a signed (trusted)
certificate, both inside a Java keystore (JKS).
Now, with Tomcat 5.5 the SSL connector refuses to start with the dreaded
keystore was tampered with
