On 16-06-29 09:08 AM, Sean Son wrote:
Hello Daniel
Thank you for the information. Here is the output of the keytool command:
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 2 entries
root, Jun 16, 2016, trustedCertEntry,
Certificate fingerprint (SHA1):
27:AC:93:69:FA:F2:52:07:BB:26:27:CE:FA:CC:BE:4E:F9:C3:19:B8
{b81d8607-57e9-4c35-a058-cd46099e7797}, Jun 16, 2016, PrivateKeyEntry,
Certificate fingerprint (SHA1):
6C:67:52:63:6B:EF:A2:3D:CD:A7:CB:64:99:99:4F:9C:3E:85:B9:AA
Is it possible that the error that I am seeing, is related to the fact that
I am using a wildcard certificate?
Thanks
I'm not familiar with this configuration. My keystore -list generates this:
***
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 1 entry
tomcat, 11-Apr-2016, PrivateKeyEntry,
Certificate fingerprint (SHA1): ...
***
That's what you should have too if you're simply following the quick
start rules here
[https://tomcat.apache.org/tomcat-8.0-doc/ssl-howto.html]. Point your
browser to "https://localhost:8443/";
I also get a browser warning when using this keystore, but it's
net::ERR_CERT_AUTHORITY_INVALID which I would expect because I haven't
registered with a root authority (i.e. it's a self-signed certificate).
I would start with that. If you then need to use an authority-signed
certificate, I personally don't have any immediate knowledge when it
comes to Tomcat, but I imagine it should be only slightly more complex.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
