Yan,
Since getTicketMapInstanceByMetadata returns IMap, you should
only need to add cas-server-core-api-ticket-6.4.4.2.jar (or whatever version
you are using).
Only one version of the library is necessary, Ticket interface is unlikely to
change much (but keep it up to date).
Ray
On Mon,
This is CAS HazelCastTicketRegistry code, it is writing to HZ IMap
object, with TGT object. I do not see any special code, it seems writing
the TGTTicketImpl object into Imap.
public void addTicketInternal(final Ticket ticket) {
val metadata = this.ticketCatalog.find(ticket);
Yan Zhou,
I would think that cas prepares the tickets prior to sending them to hazelcast.
Hazelcast should not need to know about the specifics of the data being stored.
Ray
On Mon, 2022-02-28 at 08:45 -0800, Yan Zhou wrote:
Notice: This message was sent from outside the University of
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
Hi,
I realize what maybe happening, the CAS documentation assumes embedded HZ,
HZ and CAS live in the same JVM and therefore having access to all CAS
jars.
But, our HZ is external to CAS, multiple CAS apps point to the same HZ
cluster running on separate VMs. How do I know which jars
