For now we have solved the issue by registering custom serializer for the
TransientSessionTickets which uses SerializationUtils for serialization
similar to how RedisTicketRegistry does it.
Our changes for reference:
https://github.com/Opetushallitus/cas-oppija/commit/809a7f357d74c54526e63266e6
We have encountered the same issue with CAS 6.6 and JPA Ticket Registry.
Redis Ticket Registry seems to not have this issue as it
uses org.apereo.cas.util.serialization.SerializationUtils instead of
AbstractJacksonBackedStringSerializer to serialize the tickets for storage.
Is it possible to ch
We found the same Problem on CAS 6.5.5 with a JPA-Ticket Registry and
delegation to a Microsoft AD via SAML2.
TL;DR: It seems like CAS failes to read the JSON it wrote earlier.
Inside the stored ticket is some JSON Data which gets serialized when the
ticket is stored.
When the tickets is then r
