browser open for the past two days. So anything done via CAS
>> won't give a good user experience.
>> --
>> *From:* cas-...@apereo.org on behalf of Ray Bon <
>> rb...@uvic.ca>
>> *Sent:* Wednesday, July 27, 2022 4:34:56 PM
>> *To:* cas-...@apereo.org
>> *Su
user experience.
*From:* cas-...@apereo.org on behalf of Ray
Bon
*Sent:* Wednesday, July 27, 2022 4:34:56 PM
*To:* cas-...@apereo.org
*Subject:* Re: [cas-user] ideas for persistence login session
alf of Ray Bon <
> rb...@uvic.ca>
> *Sent:* Wednesday, July 27, 2022 4:34:56 PM
> *To:* cas-...@apereo.org
> *Subject:* Re: [cas-user] ideas for persistence login session
>
> Pablo,
>
> The long running pages could be added as a service with longer TGT life,
> https://a
won't give a good
user experience.
From: cas-user@apereo.org on behalf of Ray Bon
Sent: Wednesday, July 27, 2022 4:34:56 PM
To: cas-user@apereo.org
Subject: Re: [cas-user] ideas for persistence login session
Pablo,
The long running pages could be added
Pablo,
The long running pages could be added as a service with longer TGT life,
https://apereo.github.io/cas/6.5.x/ticketing/Configuring-Ticket-Expiration-Policy.html#per-service
Ray
On Wed, 2022-07-27 at 12:16 -0700, Pablo Vidaurri wrote:
Notice: This message was sent from outside the
The ST generally should have a lifetime measured in seconds. Since it is
single use, it doesn't really make sense to issue one, have a client hold
on to it for an hour, and finally use it. The lifetime should generally
reflect the anticipated network time for the client to receive the ST and
Currently CAS TGT is an 8hr session, ST is a 2hr session. Client is
requesting to enable certain parts of their site (protected) to include a
longer ST (for weeks) while maintaining a 2hr session for other secured
parts like "Account/Profile".
I understand the application needs to change, but
