Tim, The entire login flow is implemented as a set of Spring Web Flow actions. You should merely insert another action into the flow (most likely after the service ticket generation but before the end state) that would do the checks you require.
-Scott On Mon, Feb 25, 2008 at 5:21 PM, Tim Mc Laughlin <[EMAIL PROTECTED]> wrote: > Hello, > > What we need to do is check a successfully logged-in user's account for > various things > (password aging, etc.) before sending them on to the service they are > trying to access. > If their password is going to expire soon, we display a message with the > option of linking > to our password-change application. > > On CAS 2, I have a servlet that I've substituted for the default > "serviceSuccess" > redirection. If it determines that the user doesn't need to be notified > of anything, it > continues on to the "goService.jsp" page. > > However, being unskilled with Spring, I am unsure how to duplicate this in > CAS 3.1. I > think I could probably hack this in, but I'd like to do it the "right" > way. Can someone > point me in that direction? > > Thanks, > Tim > > > _______________________________________________ > 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
