On 6/2/22 11:43, Rob Sargent wrote:
I had this overall configuration working until I 'terminated' the
AWS server instance and am trying to rebuild.
Could a lack of network connectivity between client and server
present this same symptom?
Hmm. Your SAN looks okay to me. Are you 100% sure you have that
certificate configured in Tomcat? ARe you using some other component
in front of Tomcat? You should be able to connect using:
$ openssl s_client -showcerts -connect 10.0.2.118:443
This will dump the certificate actually presented by the server. You
can copy/paste that into:
$ openssl x509 -text
and get the details to make sure the SAN appears there.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Thanks Chris, given your vote of confidence I realized I had not
updated the keystore file with my recently regenerated cert.
Also forgot to mention this is tomcat 9.0.63 embedded in my app,
running java17 (correto) at AWS
But I think I'm going backwards.
Hang on. I'm panicking. I have a plane to catch in 3 hours and need
this working by then.
ws s3 cp fullca.p12 s3://691459864434-sgs-source/certs/sgstrust.p12
splatting one file on top of the other
