Hi there, I am running into an issue with CAS cluster (active/active CAS server running on tomcat7, with load balancer in front), when we use memcached and JDBC authentication.
First of all, this works in CAS 3.5.X overlay. This also works when I use hazelcast on CAS 4.1.9 overlay. This also works with CAS 4.1.9 + Memcached + org.jasig.cas.authentication.AcceptUsersAuthenticationHandler This does not work with CAS 4.1.9 overlay + Memcached + JDBC Authenticator. I can reproduce this consistently using REST API. I get TGT and ST calling REST API on server 1, then I call /serviceValidate on server 2 to validate the ST I just got, it fails with "ticket not recognized", memcached client says "Exception waiting for values", with no further details. I verified that TGT and ST do reside in memcached. However, if I call /serviceValidate on the same server that issued ST, then it is validated successfully. As you can see, if I swap out the authenticator from AcceptUsersAuthenticationHandler to JDBC Authenticator, in my CAS 4.1.9 overlay, the memcached client can not find ST if the call is handled by a server that has not issued ST.. This is quite odd, but it leads me to believe something inside memcached client that comes with CAS 4.1.x. I now switched to Hazelcast, so far it works fine. I do not expect someone trying to reproduce this, but maybe you have an easy way to test it out. I cannot think of anything that I could miss in my configuration. Any comments? Thx, Yan -- You received this message because you are subscribed to the Google Groups "CAS Developer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.
