The SingleSignOutHttpSessionListener is used to add users¹ sessions to the map of managed sessions so the SingleSignOutFilter can invalidate / expire them whenever a Logout Request comes in due to users signing out of CAS. This is absolutely necessary for Single Sign Out purposes.
On 11/26/08 7:59 PM, "qingfeng zhang" <[EMAIL PROTECTED]> wrote: > Hi, > > I'm reading the code of Single Sign Out part and I don't understand the > function of SingleSignOutHttpSessionListen > er. > > The SingleSignOutFilter will destroy session and remove it from the map of > managed sessions, why we still need to detect the sessionDestroyed event? > > Thanks & Best Regards, > Qingfeng Zhang > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas -- Andrew R. Feller, Analyst Information Technology Services 200 Fred Frey Building Louisiana State University Baton Rouge, LA 70803 (225) 578-3737 (Office) (225) 578-6400 (Fax)
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
