It fails because for some reason RefreshScoped beans can't be serialized. In SurrogateAuthenticationConfiguration the ExpirationPolicy is defined in RefreshScope. As a workaround you should modify the bean method and remove @RefreshScope
On Friday, January 11, 2019 at 5:26:25 PM UTC+1, David McMillan wrote: > > I've been doing some testing with CAS 6.0 and found that having the > surrogate enabled with hazelcast causes a serialization issue when storing > the CAS ticket. Having either one enabled with the other disabled makes > the system work fine. We have been looking at using surrogate for our > Testing environments but in prior versions with using an LDAP attribute > repository, I had been unable to get CAS to release the attributes for the > surrogate user. Hoping this is now possible with 6.0. It wasn't working > with 5.2. > -- - 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/57d135a0-0d33-4fea-8927-af46401fab4b%40apereo.org.
