Hello -
We did this actually. But I can't be sure we did it correctly. We
created a new key using the IP address as the host, and replaced the
"a1as" aliased key in Glassfish. We loaded that certificate into the
client. But we got the same error.
I did not look at the certificate to see if al
(IANA certificate expert)
It is not clear to me do you have control over Glassfish server or not.
If you do, just generate self-signed certificate for the Glassfish one
more time, giving IP address instead of FQDN for CN.
If you don't, than you need to check does certifiate have altSubjectNam
pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Thu, 13 Aug 2009 10:54:19 -0700
> Subject: Re: SSL Using IP Addresses
> From
Hello -
We do not have permission to create a hosts file entry (that was my
first idea).
We also do not need both IP address and host name to work at the same
time, just the IP address. Our problem seems to be that the Tomcat
client wants to find a certificate by hostname, even when the URL
requ
Jeff Sexton wrote:
We have a situation where we need to call a SOAP service in a
Glassfish server via HTTPS from a servlet in Tomcat. We extract a
self-signed certificate from Glassfish and imported it on the Tomcat
server. It all works in situations where we can use the
fully-qualified host na
Hello -
We have a situation where we need to call a SOAP service in a
Glassfish server via HTTPS from a servlet in Tomcat. We extract a
self-signed certificate from Glassfish and imported it on the Tomcat
server. It all works in situations where we can use the
fully-qualified host name in the re
