Did you find a solution for this issue? I am facing the same problem in CAS 6.1.5 with JDBC backed AUP storage. With 5.3 everything worked fine.
Best regards, Udo Am Montag, 23. September 2019 22:20:15 UTC+2 schrieb jbstowe22: > > I am working on implementing the acceptable use policy in 6.x (I have > gotten the issue in 6.0.2+ and all the 6.1 RC's) with ldap being the > backing storage. Everything works fine up until the point where you agree > to the policy, once you click the accept button the aup ldap attribute gets > updated to true as expected and the page redirects but it still sees the > aup attribute as false. I have made sure attribute caching is disabled and > that the aup attribute is available through normal attribute resolution. Am > I missing something to force the principal attributes to update during that > redirect? > > Interestingly enough version 6.0.1 works perfectly, but I don't want to be > forced to use 6.0.1 forever. > > Any help would be appreciated, thanks! > -- - 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/5baef1e9-6e47-43bf-9305-ff5c7827766e%40apereo.org.
