Hi, Correct me if I'm wrong but it looks as Redis caching is cleaning up objects on its own ... based on the ticket TTL https://apereo.github.io/cas/7.0.x/ticketing/Redis-Ticket-Registry.html As I'm interested in this topic, I'll keep on an eye on following answers to get more accurate info ... Regards,
Le jeudi 14 novembre 2024 à 14:43:31 UTC+1, wouldsmina a écrit : > Hello, > > I have set up CAS to perform a cleanup of the ticket registry (Redis), but > at startup, I get a message saying that it is not enabled: > 2024-11-14 14:26:21,575 INFO > [org.apereo.cas.config.CasCoreTicketsSchedulingConfiguration] - <Ticket > registry cleaner is not enabled to run on schedule. Expired tickets are not > forcefully cleaned by CAS. It is up to the ticket registry itself to clean > up tickets based on its own expiration and eviction policies.> > > cas.properties : > cas.ticket.registry.cleaner.schedule.cron-expression=0 0 0 * * * > cas.ticket.registry.cleaner.schedule.enabled=true > > CAS Version: 7.1.2 > Java Version: 21.0.5 > Tomcat Version: 10.1.6-1+deb12u2 > > Did I forget a parameter in the configuration ? > > Wouldsmina. > -- - Website: https://apereo.github.io/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/5c11c411-70ba-4db1-aa82-95302e16ee1cn%40apereo.org.
