Yes, the HTTP is the problem. Switched to HTTPS and it started printing the logout events.
Thanks a lot for your help. OC. Scott Battaglia wrote: > Also, are you running the CAS over SSL? If you're not then you may not > be sending the cookie back to the server on logout. > > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: http://www.linkedin.com/in/scottbattaglia > > > > On Fri, Nov 7, 2008 at 5:12 AM, Oh Calcutta <[EMAIL PROTECTED]> wrote: > >> Thanks Scott for your reply. >> >> I am on CAS 3.2.1 on Jboss 4.2.3 now, where I see these events printed on >> signout. >> >> I don't have access to the workstation which didn't print this on logout. I >> must have done something wrong. I will double check the configuration. >> >> OC. >> >> Scott Battaglia wrote: >> >> The only way it wouldn't show up is if the method wasn't called. I >> just confirmed in our logs that they do appear. >> >> -Scott >> >> -Scott Battaglia >> PGP Public Key Id: 0x383733AA >> LinkedIn: http://www.linkedin.com/in/scottbattaglia >> >> >> >> On Thu, Nov 6, 2008 at 1:40 PM, Oh Calcutta <[EMAIL PROTECTED]> wrote: >> >> >> CAS Server : 3.3 on apache-tomcat-5.5.26 >> >> Hi, >> >> I copied auditTrailContext.xml (without any modification) to >> spring-configuration directory and restarted the server. When I log in, >> details get printed in console (WHO WHAT ACTION... etc). However, when >> logout is called, nothing comes in the console like >> TICKET_GRANTING_TICKET_DESTROYED as found in >> 'CentralAuthenticationServiceImpl'. Am I missing something? >> >> Thanks, >> >> OC. >> _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
