Thanks to all who replied. I got side tracked by other issues and when
I returned to this one I found that some services worked consistently
and one (cas-managment version 6.1.x) was problematic. So it turns out
that hazelcast was working.
Thanks for the clarification on distributed vs
Fernando's message below is great advice. The version of the CAS server
isn't going to matter too terribly much. It will depend on what protocol
you are planning to use against CAS. I'm going to guess CAS Protocol v3,
which gives you everything you need. You are going to want a security
This is just a thought. I'm in kind of the same position as you are. I was
given the task to implement SSO and SLO for our apps even though I'm rather
inexperienced and been working with Spring for less than a year.
I don't know exactly which versions of either Spring, Java nor CAS you are
Hi all,
Finnally I found out the solution.
The way I mentioned in the first email is not possible to work from start,
because Spring AOP only works when your pointcut is on a Spring bean.
ClientInfoThreadLocalFilter is registered by an instance of
FilterRegistrationBean so the instance is
