Thank you all for your help. It just came to a point where I just had to
delete the old keystore and create a new one, and request for new
certificates. Now everything's working.
On Tue, Sep 17, 2013 at 9:58 AM, Jan Vávra wrote:
> Maybe it'd helpful not using the java key store (JKS).
> Persona
Maybe it'd helpful not using the java key store (JKS).
Personally on Linux Tomcat installations without native APR I use the
.p12 files with this config
maxThreads="150" scheme="https" secure="true"
clientAuth="false" sslProtocol="TLS"
keystoreFile=${catalina.hom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ognjen,
On 9/17/13 4:37 AM, Ognjen Blagojevic wrote:
> Mavenpol,
>
> On 16.9.2013 22:47, Mavenpol Saulon wrote:
>> This server where I imported the certificates and has been
>> encountering errors is just one of the servers that are
>> configured t
Mavenpol,
On 16.9.2013 22:47, Mavenpol Saulon wrote:
This server where I imported the certificates and has been encountering
errors is just one of the servers that are configured to run SSL. All of
the other servers have the same setup except for the "keytool -delete.."
that I used in this parti
Thanks Jan for replying. Unfortunately, I'm not inclined on going to the
direction that it's a browser problem.
This server where I imported the certificates and has been encountering
errors is just one of the servers that are configured to run SSL. All of
the other servers have the same setup exc
|Hello,
on http://support.mozilla.org/cs/questions/952242 there is described
smthg about ssl protocol settings for Firefox. It seems like you
have configured ||in server.xml||eg. only SSLv2 protocol that is
disabled in the client browser
http://tomcat.apache.org/tomcat-7.0-doc/config/htt
Good Day!
Everything was followed perfectly from this URL:
http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html. I've done this
setup a lot of times already and mostly I have been successful.
Until our security team noticed that the installed root CA is incorrect.
Instead of just importing the
