Has anyone else run into problems with tickets piling up with the MongoDBTicketRegistry? For me tickets are not deleted unless the session ends gracefully, i.e. the user explicitly logs out and the logout webflow is triggered.
Looking at the source of MongoDBTicketRegistry it seems like the TTL index isn't being handled properly. The expireAt field that the index is created against seems to always be set to the ticket expiration seconds. The way I understand Mongo TTL indexes is that they are created against datetime field. Am I missing something or should the expireAt field hold the date time that the ticket should expire rather than the number of seconds to expire? -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/de5b2244-9c76-4da0-83a2-f23e469538e9%40apereo.org.
