Yan, We use two different approaches. Some apps have a common session store like redis. Other applications are configured to propagate the log out to all members of the cluster, but this is only practical for a small cluster.
If your application runs in a container, maybe it can manage session replication (tomcat can do this). Another, maybe less desirable option, perhaps the load balancer can look for /logout and broadcast to all members of the cluster. Ray On Tue, 2019-04-02 at 07:53 -0700, Yan Zhou wrote: Hello! CAS4, for SLO, CAS server POSTs (back-channel SLO) to each service to perform SLO. It works because there is a CAS client in the application that intercepts such SLO requests, it can find the app. session Id based on the CAS service ticket Id. Is there any requirement on the part of Application to support SLO in a cluster environment? Our app. runs on multiple servers behind a load balancer, it uses CAS for authN. The problem, I run into, is that when App /logout endpoint gets called, it does not know where App Session is, the load balancer may direct the app /logout on the server not having the application session. Am I missing something? Thx! Yan -- Ray Bon Programmer analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected] -- - 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/1554218540.3128.24.camel%40uvic.ca.
