Adam, I encountered the same issue whenever I deployed CAS 3.0.7 / 3.1.0 as I needed CAS to create and destroy an additional cookie upon login / logout. At the time, the only solution available was to create a custom Spring WebFlow state for the login process and extend the logout controller to expire my cookie upon logout.
I am perfectly aware that this isn't elegant or desirable as I am dealing with upgrading to CAS 3.2.1, so I would love to hear a solution, too! I am available for private conversation about this if you want to talk more. Thanks, Andy Andrew R Feller, Analyst University Information Systems 200 Fred Frey Building Louisiana State University Baton Rouge, LA, 70803 (225) 578-3737 (Office) (225) 578-6400 (Fax) ________________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Rybicki Sent: Wednesday, May 07, 2008 9:01 PM To: Yale CAS mailing list Subject: Re: How to integrate a login & logout event listener in CAS Server ? Scott, I am back from the conferences and resolving this issue has come to the top of my priority list. I spent some time looking at 3.2.1, and I have not been able to figure out how to weave my custom code into this new package. Let me elaborate... My custom code needs to perform some work when a TGT is created or destroyed. I looked at the sample auditTrailContext.xml. This sample has no comments that would hint at "hooking in" custom auditing code. I am not schooled in AOP, and while I understand the concepts, some additional hints would help. I just do not see how to configure the system to notify my code of TGT creation and destruction. CAS manual on the JA-SIG Wiki has nothing on the subject. Can you please point me in the right direction? Thanks, Adam Scott Battaglia wrote: We switched to the Inspektr package for a few reasons: 1. It provides end-to-end auditing, it can track user, ip address, and action all in one transaction 2. its an open-source library developed by two coworkers and myself that can be incorporated into other projects, allowing for knowledge re-use. Eventually the tool will include a web application to view the results. 3. supports statistics gathering 4. code is completely externalized from the CAS code so enabling/disabling it adds/removes the code rather than the events being fired anyway and then ignored 5. its generic so we can add new things to audit without creating new events 6. The code in the source tree was actually sample/example code on how to do auditing using events, and not designed for production use (though it was capable of being used that way). We stated this when it was put in place in 3.0, but I'm sure by now everyone's forgotten about that :-) -Scott On Tue, Apr 22, 2008 at 4:18 PM, Adam Rybicki <[EMAIL PROTECTED]> wrote: Scott, Was there anything wrong with EventHandler or TicketEvent? I ask because I have used them, and now upgrading to 3.2.1 will be more difficult. :-( Adam Scott Battaglia wrote: Cyrille, Since CAS is now using the Inspektr package (detailed here: http://code.google.com/p/inspektr/) that's our preferred way of doing things. You'll merely need to write an AuditTrailManager that does the JMS call. -Scott On Tue, Apr 22, 2008 at 6:14 AM, Cyrille Le Clerc <[EMAIL PROTECTED]> wrote: Hello, I would like to capture login and logout events in CAS Server to broadcast these events to a JMS Topic (backend data preloading, etc). The package org.jasig.cas.event (AuthenticationEvent, TicketEvent and EventHandler interface) has been removed in CAS 3.2, the SVN comment says "started move to Google Code Inspektr library". What is the preferred way to integrate a login/logout/ticket event listener in CAS ? Thanks in advance, Cyrille -- Cyrille Le Clerc [EMAIL PROTECTED] [EMAIL PROTECTED] Mobile : +33 6.61.33.69.86 http://blog.xebia.fr _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas -- -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia ________________________________________ _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas -- -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia ________________________________________ _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
