Fazla,
This is what I have in my config
## default is P14D
## used to set maxAge on user selection of remember me at login
## it is always set regardless of user choice; this is a bug to investigate
## file:
Hi Fazla,
Unfortunately i'm unsure what cas.tgc.rememberMeMaxAge is used for and how
it differes from cas.ticket.tgt.rememberMe.timeToKillInSeconds=
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
-
Hi John,
Thanks for your reply. I saw your configuration and I will try this in our
staging environment. I was wondering about cas.tgc.rememberMeMaxAge properties,
what does that do? Also if this config works for you please let me know.
Thanks. Regards
On Thu, Jun 4, 2020 at 5:31 PM John Bond
Hi Fazla,
We use are now using the following settings
cas.ticket.tgt.rememberMe.enabled=true
cas.ticket.tgt.rememberMe.timeToKillInSeconds=604800
cas.ticket.tgt.timeToKillInSeconds=3600
cas.ticket.tgt.maxTimeToLiveInSeconds=604800
We are still testing but the intention is that someone who sets
Hello John and Ray,
We are also using memcached as a ticket registry and facing the same issue
as the remember me functionality not working properly as expected. Below
is our configuration. Are you doing anything wrong.
cas.ticket.tgt.rememberMe.enabled=true
Ray
On Tue, Jun 2, 2020 at 6:04 PM Ray Bon wrote:
> John,
>
> I think timeout.maxTimeToLiveInSeconds provides a sliding window with no
> defined stop time.
>
Ahh thanks, This now makes sense why
org.apereo.cas.ticket.expiration.TimeoutExpirationPolicy
returns Long.MAX_VALUE for its TTL
> I
John,
I think timeout.maxTimeToLiveInSeconds provides a sliding window with no
defined stop time.
I set our remember me to the same as maxTimeToLiveInSeconds, so do not know if
it provides a sliding window.
Ray
On Tue, 2020-06-02 at 12:31 +0200, John Bond wrote:
Notice: This message was sent
Hi Ray,
Thanks for the explanation this is very helpful, i'd like to update our
documentation[1] and want to ensure i understand this correctly. Is the
following be correct
# Timeout level
If maxTimeToLiveInSeconds is specified at the timeout level as in the
following example, then it takes
John,
Timeout has higher priority than Default.
timeout.maxTimeToLiveInSeconds is a more general approach (an application like
an webmail client, that hits cas every 10m when it checks for new mail, will
keep the TGT alive while the tab is open).
The two settings in Default,
Hi Ray,
Thanks for the response however ...
On Mon, Jun 1, 2020 at 6:16 PM Ray Bon wrote:
> John,
>
>
> https://apereo.github.io/cas/6.1.x/ticketing/Configuring-Ticket-Expiration-Policy.html
>
> timeout.maxTimeToLive... is a hard timeout. The other is a 'must be used
> within this time' to be
John,
https://apereo.github.io/cas/6.1.x/ticketing/Configuring-Ticket-Expiration-Policy.html
timeout.maxTimeToLive... is a hard timeout. The other is a 'must be used within
this time' to be valid. If the TGT is used within this window, the validity
will extend by that time up to
Hello All,
In out config we set both cas.ticket.tgt.timeout.maxTimeToLiveInSeconds and
cas.ticket.tgt.maxTimeToLiveInSeconds to the same value believing theses
where the same and made a note to validate this with this group[1]. That
later step never happened and the config remained. however
12 matches
Mail list logo
