I'm having trouble accepting an out-of-band solution for cleaning up security data. This clean up is part of ticket expiration policy enforcement, right? If so it should clearly be handled by CAS.
I'm still not clear whether the "previously reported issue" Adam mentioned is a performance problem or error condition such as Ryan reported. Can anyone provide any further information on this? We are planning on using JpaTicketRegistry for our upcoming deployment, thus my interest in the issue. Thanks, Marvin -- 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
