I get it now. Here is something very weird After reconfiguring all the changes on my test environment(it works fine now), I wanted to make the same changes to production environment, but instead I just reinstalled Tomcat as a service and the 'Unable to validate ProxyTicketValidator' error message did not show up.
As a result I am confused right now,because yesterday I made changes to increase the heap size in Tomcat and modified the service.bat file that comes with Tomcat.(Also the JAVA_OPTS environment variable is modified) ---- I know this has nothing to do with CAS, but today, I started getting the ProxyTicketValidator Error. To fix this on the production server I just resinstalled service.bat as a windows service and the error was gone. I spent more than 4 hrs and got a good solution and understanding of the ProxyTicketValidator and SSL trust issue but seems like the error was misleading (because I only changed environment variables for increasing heap size). Thank You, Kavita On Tue, Jul 21, 2009 at 2:54 PM, Marvin Addison <[email protected]>wrote: > > But the Tomcat documentation does not mention that. > > It has nothing to do with Tomcat, so would not be mentioned in that > context. The "infamous" ProxyTicketValidator you are getting is > caused by a connection initiated by a Java class to the CAS server. > The root cause an SSL trust issue between the JVM running your > application and the certificate presented by the CAS server. The > system keystore, $JAVA_HOME/jre/lib/security/cacerts, is the keystore > that matters in that case. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- Kavita Tipnis -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
