Hi Chris - No luck finding a solution on the error, however the good news is other than polluting our logs (which we could mitigate) there does not appear to be any negative user impact.
We're several million authentications into this upgrade without any users reporting issues. On Wednesday, January 22, 2020 at 9:45:40 AM UTC-5, Christine Pasek wrote: > > Hello Josh, > > I have just upgraded from 5.2.X to 5.3.X and am experiencing the same > error and like you, everything seems to be working fine. > > Were you able to find a solution to fixing this error? > > Thanks! > Chris > -- - 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/a5632664-a375-4e32-8776-abaf6058218e%40apereo.org.
