The TGC settings deal with the CAS session when the browser is redirected to log in a service and can be set to live beyond browser closing. The TGT is the session on the CAS server; it is used for log in (obviously) but also back channel communication such as proxying. I do not know what use having cas.tgc.rememberMeMaxAge expire after a cas.ticket.tgt.rememberMe.timeToKillInSeconds. I have not tested this but I suspect the log in screen would be displayed and a new cookie would be issued.
cas.ticket.tgt.rememberMe.timeToKillInSeconds can be used with other tgt setting to create sliding windows of [log in] activity, etc. https://apereo.github.io/cas/5.2.x/installation/Configuration-Properties.html#tgt-expiration-policy Ray On Tue, 2018-08-28 at 02:44 -0700, vallee.romain wrote: Thank Rbon. now, if i want this : if users check "rememberme", they don't need to get autentication while 1 month . do you know how ? if "TGT" expires, will "TGC" expire? what differences between: cas.ticket.tgt.rememberMe and cas.ticket.tgc.rememberMe I don't find anywhere documentation about this process . Thank you very much Le lundi 27 août 2018 18:53:06 UTC+2, rbon a écrit : Vallee, When you say session, are you talking about the CAS session or the client session? Is it possible to have a cookie that expires when the browser closes and lives for a set time? You can use this to have the cookie expire when the browser closes: cas.tgc.maxAge=-1 I have this note in my config (not sure if it applies to 5.2) but our config is set to expire TGC when browser closes: # 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: https://github.com/apereo/cas/blob/5.1.x/support/cas-server-support-cookie/src/main/java/org/apereo/cas/web/support/CookieRetrievingCookieGenerator.java<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fapereo%2Fcas%2Fblob%2F5.1.x%2Fsupport%2Fcas-server-support-cookie%2Fsrc%2Fmain%2Fjava%2Forg%2Fapereo%2Fcas%2Fweb%2Fsupport%2FCookieRetrievingCookieGenerator.java&sa=D&sntz=1&usg=AFQjCNGfyK2U3hOc1g4j-auWb5SNrX7i5w> cas.tgc.rememberMeMaxAge=-1 I do not have these in my config: cas.ticket.tgt.timeToKillInSeconds cas.ticket.tgt.maxTimeToLiveInSeconds Ray On Mon, 2018-08-27 at 02:51 -0700, vallee.romain wrote: Hello, We have migrate from 4.2 to 5.2. Our need is simple, but we can't implement it . We put the option "remember me", with a delay of 6 months ( about). But even following the documentation, it is impossible to have a session maintained for more than a few hours by checking the "remember me" box. i try so many configuration... my last configuration is : cas.tgc.rememberMeMaxAge=1209600 cas.ticket.tgt.timeToKillInSeconds=172800 cas.ticket.tgt.maxTimeToLiveInSeconds=1350000 cas.ticket.tgt.timeout.maxTimeToLiveInSeconds=1350000 cas.ticket.tgt.rememberMe.enabled=true cas.ticket.tgt.rememberMe.timeToKillInSeconds=1350000 did anyone manage to make it happen: when you check "remember me" to have a session maintained for XX months when you do not check "remember me" with the session that closes at the end of the browser with a maximum time of XX hours. I'd be very interested! Best regards -- Ray Bon Programmer analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected]<javascript:> -- Ray Bon Programmer analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected] -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/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 on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/1535476514.2864.27.camel%40uvic.ca.
