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
Em quinta-feira, 13 de o
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
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
On Wednesday, October 12, 2022 at 1:40:27 PM UTC-7 robin@gmail.com
wrote:
> Hello,
>
> I'm struggling to upgrade a CAS server from 6.5.
Hi Andrea,
Our JPA service registries for 5.2 and 6.5 are both in an Oracle database;
separate schemas.
After a lot of back and forth, I ended up reverse-engineering the 5.2 field
structure and exported just the bits that we needed as JSON fields to the
6.5 database.
The following SQL does the tran
Hi Steine, does it works your test ?
Il giorno martedì 28 giugno 2022 alle 23:14:27 UTC+2 steine...@gmail.com ha
scritto:
> We are currently upgrading from v5 to v6 and use JPA like you are. What
> we are doing is to use the CAS5 endpoint /status/services/export to get a
> zip file of all ou
Hi Trevor,
how do you resolve finally ?
We have the same situation starting from 6.1 to 6.5
Bye
Il giorno venerdì 3 giugno 2022 alle 22:45:26 UTC+2 Trevor Fong ha scritto:
> Hi Everyone,
>
> Along the same lines as
> https://groups.google.com/a/apereo.org/d/msgid/cas-user/75ef5b42-d3b7-366b-8b5
