-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Miguel,
On 4/25/12 4:09 PM, Miguel González Castaños wrote: > I've downloaded the certificates as veriCA1.cer and veriCA2.cer and > run: Do those certificates match the type of certificate that you have? Last time I checked, VeriSign had a whole set of intermediate certificates and you need the ones that match the type of certificate you have (EV versus whatever the other flavors they have are). > keytool -import -trustcacerts -alias EV_root -keystore > /opt/tomcat5/certs/tcc -file veriCA1.cer Is /opt/tomcat5/certs/tcc the file you have configured in Tomcat? Please post your SSL <Connector> configuration (cleansed of any passwords). Finally, you didn't post your original stack trace. Since this is happening on the server-side, it's either a problem during startup or during client-certificate verification. Since you mentioned the "site certificate", I assume you are having problems with your server's SSL certificate and not a client certificate being presented by a remote client, right? Can you show me what this command returns: $ keytool -list -keystore /opt/tomcat5/certs/tcc -v - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+Yd2UACgkQ9CaO5/Lv0PDUcgCgg90suQAZyF1XEivzFJ/8kB5g 8bAAoI+2TDx6N/WWegOmFYY1caiwvrbC =Ky/W -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
