Upgrade from CAS 6.5 to 6.6

[Robin Dupret]

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.

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.

[Trevor Fong]

Hi Robin,

I'm afraid I don't have a fix for you, but I also experienced these errors when trying to upgrade to 6.6.x;  I went to 6.5.8 instead.

Thanks,

Trev

[Dmitriy Kopylenko]

This is related to deprecation of RegexRegisteredService type as described here in the released notes: 

https://apereo.github.io/cas/6.6.x/release_notes/RC3.html#cas-registered-services

If you are using JSON service registry, make sure to change all the service types from RegexRegisteredService to CasRegisteredService. 

D. 

--
- 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 cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/97a2b2ba-85c7-418b-a46a-eae4a43ccd1cn%40apereo.org.

[Irineu Ruiz]

Hello, we had a similar problem with version 6.6.0 but only asking for many tickets simultaneously for the same service with the same user.

In our case, we were able to solve this with the following configuration:

cas.ticket.tgt.core.only-track-most-recent-session=false

[Robin Dupret]

Hello,

> This is related to deprecation of RegexRegisteredService type as described here in the released notes

That was it ! 🎉

Thank you very much everyone for your answers !

[Pascal Rigaux]

Hi,

Since "RegexRegisteredService" does not work anymore
(since https://github.com/apereo/cas/commit/befb293909418fc49afc602382d6d57d64394187#diff-038da8b55c081ccedb1604bbaaa8baed54e070dc9d71c661cfdc207fa5324aa1 )
what about turning the warning "deprecated" into error "removed"?
(in https://github.com/apereo/cas/blob/6.6.x/core/cas-server-core-services-api/src/main/java/org/apereo/cas/services/RegexRegisteredService.java#L26-L30 )

cu

On 13/10/2022 22:58, Dmitriy Kopylenko wrote:
> This is related to deprecation of RegexRegisteredService type as described here in the released notes:

> https://apereo.github.io/cas/6.6.x/release_notes/RC3.html#cas-registered-services <https://apereo.github.io/cas/6.6.x/release_notes/RC3.html#cas-registered-services>

>
> If you are using JSON service registry, make sure to change all the service types from RegexRegisteredService to CasRegisteredService.
>
> D.
>