I have implemented that feature using Acegi Security/Spring Security approach in my authentication handler implementation, this is the first step that you need to do, and there are three options:
1- store sessions information like Acegi Security/Spring Security thats in a Map 2- traverse the ticket registry finding the user session previous authenticated 3- store sessions information in a database table The three options need a clean user logout because the feature you are looking for are blocking multiple authentications and if you not delete sessions information your users cannot login in your app and you would need to have an session management to kill user sessions -- 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
