Niral,
I still kinda thing the same as before, i.e. that the TGC cookie is simply
rejected by your browser. Because when you do the refresh of the login page
(e.g. pressing F5 instead of hitting Enter in the address line) , you're
re-sending the login credentials and that's why you see "you
Baron,
I have used the cas source and spring api docs to understand see what these
objects hold.
They are all complex objects and I print their contents to the logs to find
what is available (it is a tedious process).
Ray
This is from one of our scripts:
class MfaSelector {
def String
Thanks, for the pointer. I did find this fairly old Fawnoos article <
https://fawnoos.com/2018/04/23/cas-access-strategy-url-redirects/>, but it
seems to describe a strategy that is perhaps even more low level that the
Groovy script suggested in the more current documentation.
One aspect I have
Niral,
To see a list of all cas properties:
$ ./gradlew exportConfigMetadata
Which will create a file called config-metadata.properties
You can search for 'tgt' or 'tgc'
The default value will be shown beside the property.
TicketGgrantingTicket is the server side session and TGC is the client
Also,
I am using tomcat server 9.0.30 on our test environment, does it can be issue?
Thankyou,
Niral
From: Niral Kunadia
Sent: Wednesday, July 5, 2023 11:28 AM
To: cas-user@apereo.org
Subject: RE: [cas-user] CAS session management - Ticket Expiration Policies -
CAS 6.5
Ray,
I am upgraded CAS
Ray,
I am upgraded CAS to 6.6.9 from 6.5.8, I am able to login to cas with
authentication and on refresh somehow TGC is expiring and asking for login
credentials again.
Is there any setting I have to add in cas.properties?
I did these steps:
1. Copy cas.war to test environment. Restarted
