Thank you very much for your help.
In my situation the probleme was that i' ve generate a bad certificate.
When the java keytool ask me the question what' s your name
i need to set this value with the name of my server (in my case with
localhost)
and not MY name ;)
So now all woks fine.
On
Thank you very much for your help.
In my situation the probleme was that i' ve generate a bad certificate.
When the java keytool ask me the question what' s your name
i need to set this value with the name of my server (in my case with
localhost)
and not MY name ;)
So now all woks fine.
And
I' m use CAS for SSO solution.
I' ve create a certifiacte for my tomcat and deployed my two applications
(CAS server AND client) on the same Tomcat with certificate.
You might want to take a look at this:
http://shib.kuleuven.be/docs/idp/install-idp-1.3-windows2003.shtml#trust
we use the JVM's
Hi,
I' m use CAS for SSO solution.
I' ve create a certifiacte for my tomcat and deployed my two applications
(CAS server AND client) on the same Tomcat with certificate.
When i go to my client application i' m redirecte (in https mode) to the CAS
server login page with aknowledge of my
Yawn, set truststoreFile=/path/to/keystore/file on the Connector /
element.
In most cases, the truststore and keystore are different authorities, so
there is no good reason for Tomcat to default them to being the same.
David Avenante [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
