Also note the schema changes for CAS 6.5, all is tickets are serialized to
one maybe two tables.
On Monday, February 28, 2022 at 10:11:44 AM UTC-6 Yan Zhou wrote:
> Hi there,
>
> Anyone having to deal with token/ticket storage that require serializing
> CAS objects like Hazelcast?
>
> For instance, TGT, ST, OIDC RT/AT all go to Hazelcast ticket registry,
> which requires to serialize any objects put on IMap.
>
> Would I have to package all jars containing these class and place on
> hazelcast lib folder?
>
> These classes are non-trivial, always have a tree of other objects, how
> do you deal with
> that?
>
> Below is an example of TGT in CAS5, let alone the other objects in
> CAS5/CAS6, etc.
>
> Thanks,
> Yan
>
>
> public class TicketGrantingTicketImpl extends AbstractTicket implements
> TicketGrantingTicket {
>
> /**
> * Unique Id for serialization.
> */
> private static final long serialVersionUID = -8608149809180911599L;
>
> /**
> * The authenticated object for which this ticket was generated for.
> */
> @Lob
> @Column(name = "AUTHENTICATION", nullable = false, length =
> Integer.MAX_VALUE)
> private Authentication authentication;
>
--
- 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/78390a98-969f-45a2-ad83-d90a97403d98n%40apereo.org.
