Filip, Ehcache is rather slow at storing/distributing tickets. If validation is done on a different server than where ticket was created, CAS will think ST is invalid.
You could set your CAS servers to be primary/secondary rather than round robin on your load balancer or switch to a different cache system. Ray On Fri, 2019-08-30 at 07:22 -0700, Filip Majernik wrote: Hello, I am using the EhCacheTicketRegistry, within an instance of CAS 5.1.1. Our performance tests of the application showed, that about a 50% of our log-in request fail. The reason for that is that sometimes the service ticket is not found in the ticket registry, although it has been successfully generated and put there (I can see it in the logs). I have managed to reproduce this behavior even manually with two browsers. If I login quickly from two separate sessions, sometimes the second login attempt fails on the validation of a service ticket. If I do not use the EhCacheTicketRegistry, this issue dissappears. Is there maybe some configuration, which I am missing? Thx, Filip. -- Ray Bon Programmer Analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected]<mailto:[email protected]> I respectfully acknowledge that my place of work is located within the ancestral, traditional and unceded territory of the Songhees, Esquimalt and WSÁNEĆ Nations. -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/5471439968b04ef9f58bc965ef26f04c890dadd7.camel%40uvic.ca.
