Hi Petr,
Thank you for your input. We upgraded from version before CAS v6.6.0-RC4
and the issue is related to the thread you mentioned. We are trying to
proceed by removing the tickets deletion logic
(beforeTrackingServiceTicket() method) from AllServicesSessionTrackingPolicy
class
as below:
public String trackTicket(final Ticket ownerTicket, final Ticket ticket) {
val serviceTicket = (ServiceTicket) ticket;
val ticketGrantingTicket = (TicketGrantingTicket) ownerTicket;
val trackedEntry = String.format("%s,%s", serviceTicket.getId(),
serviceTicket.getService());
lock.tryLock(__ -> {
ticketGrantingTicket.update();
serviceTicket.getService().setPrincipal(ticketGrantingTicket
.getRoot().getAuthentication().getPrincipal().getId());
System.out.println("This is trying to delete the PTs of the PGT:" +
ticketGrantingTicket.getId());
System.out.println("But we have commented this");
*// beforeTrackingServiceTicket(ownerTicket, serviceTicket);*
ticketGrantingTicket.getServices().put(serviceTicket.getId(), serviceTicket
.getService());
});
return trackedEntry;
}
On Saturday, March 7, 2026 at 9:53:15 PM UTC+5:45 Petr Bodnár wrote:
> Hi Prakash,
>
> did you upgrade from a version before CAS v6.6.0-RC4? Then I think you've
> hit the infamous problem described in this thread: CAS 6.6.8 invalid ST
> <https://groups.google.com/a/apereo.org/g/cas-user/c/oRbsZsJwY1A/m/T-IZhycBBQAJ>.
>
> The thread talks about service tickets and TGT, but I would expect it
> relates to proxy tickets and PGT as well.
>
> Regards
> Petr
>
> On Friday, 6 March 2026 at 15:59:53 UTC+1 Prakash Thapa wrote:
>
>> In older version of CAS, we noticed that the multiple Proxy Tickets can
>> be created and can co-exists in CAS Ticket Registry till it is expired or
>> validated, even though they are generated using same PGT.
>>
>> But in CAS 7.2.4, we noticed that once a new Proxy Ticket is created, the
>> older PT generated from same PGT is automatically removed from the Ticket
>> Registry. We are running multiple threads, and making multiple microservice
>> calls, each microservice is protected by CAS, and holding/using the same
>> PGT till it is valid to generate the Proxy Tickets.
>>
>> Due to this behaviour few of the service calls are failing in upgraded
>> CAS as a single PT is stored in Ticket Registry. *Can it be configured
>> or updated so that the multiple Proxy Tickets generated from same PGT could
>> co-exist? We are using Redis Ticket Registry*.
>>
>> Regards,
>> Prakash
>
>
--
- Website: https://apereo.github.io/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 visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/b3fa9143-919b-4933-89fe-78954a232fd4n%40apereo.org.
