Mark Thomas [mailto:[EMAIL PROTECTED]
Sent: Friday, January 16, 2004 5:20 PM
To: 'Tomcat Users List'
Subject: RE: Using CA-issued certificates in Tomcat 5
Try this - don't delete the alias before importing the response.
What happens is:
keytool -genkey -alias tomcat -keyalg RSA
Creates your
To: [EMAIL PROTECTED]
Subject: RE: Using CA-issued certificates in Tomcat 5
keytool in JDK 1.4.2_03 no longer seems to accept PKCS#7
certificates by default and I have not found a parameter to
tell it to use them.
When I do as you suggested (or download a Thawte pkcs#7
certificate) I
and tomcat.
-Original Message-
From: ext Mark Thomas [mailto:[EMAIL PROTECTED]
Sent: Monday, January 19, 2004 12:38 PM
To: 'Tomcat Users List'
Subject: RE: Using CA-issued certificates in Tomcat 5
I am using 1.4.2_03 without any problems and have successfully imported various
certs (versign, self
Try this - don't delete the alias before importing the response.
What happens is:
keytool -genkey -alias tomcat -keyalg RSA
Creates your private and public key
keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr
wraps a copy of your _public_ key in a certficate request
... got the
Needless to say, you have to use the same key that you used to generate the
CSR that you sent to Verisign/Thwate. It looks like you nuked the key when
you did the delete.
[EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I thought I had all my Tomcat issues resolved and was ready to go
