Mark,
It turns out that the root certificate was a combination of g1 and g2, and that
this causes a problem for keytool. I downloaded the single root certificate
gdroot-g2.crt and used it to replace the root certificate. That fixed the
problems.
Jeff
Sent from Windows Mail
From:
I’ve been using Tomcat for about fours years. I’ve developed websites and
services that used certificates based upon SHA1. Today I purchased a new
certificate from GoDaddy based upon using “-sigalg SHA256withRSA”.
So for this new service I executed the following commands in the directory of
keytool -delete -alias tomcat -keystore tomcat.keystore
You deleted the key at this point. There should be no need to do this.
Mark
Mark,
I rekeyed my certificate from a newly created tomcat.keystore and imported in
the root and immediate certificates, then I got this when I imported my
On 7 August 2015 19:01:34 BST, jeffery.scott.cr...@gmail.com wrote:
I’ve been using Tomcat for about fours years. I’ve developed websites
and services that used certificates based upon SHA1. Today I purchased
a new certificate from GoDaddy based upon using “-sigalg
SHA256withRSA”.
So for this
