Hello, I'm struggling to upgrade a CAS server from 6.5.9 to 6.6.1. The problem is that service tickets are always invalid. There's an INVALID_TICKET response sent (with "Ticket ... is not recognized") calling serviceValidate.
Here's my environment : * Debian 11 * Tomcat 9.0.43 (provided by Debian, managed by Systemd) * Java 11 (OpenJDK build 11.0.15+10-post-Debian-1deb11u1) The CAS server initially relied on a Redis storage for storing tickets but it neither works with the default in-memory storage. TGT are properly stored though but I can't see service tickets. It looks like there is a regression between `6.6.0-RC5` and `6.6.0` (because 6.6.0-RC5 works but not 6.6.0). I can't manage to find where does it stem from skimming the Git history between these two versions <https://github.com/apereo/cas/compare/v6.6.0-RC5...v6.6.0>. Here are the versions tested that *do* work : * 6.5.5 * 6.5.9 * 6.6.0-RC1 * 6.6.0-RC2 * 6.6.0-RC5 (6.6.0-RC3 and RC4 seem broken, all services tested are considered unauthorized to use CAS ...) These versions don't work though : * 6.6.0 * 6.6.1 The versions have been tested with the exact same cas-overlay-template ; the gradle.properties has just been changed to modify `version` and `cas.version` (and to stick `springBootVersion` to 2.6.3). Could you help me debug/fix that please ? Have a nice day. -- - 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/7d497a11-ebec-4bf3-be30-f9b4666f338bn%40apereo.org.
