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
I should add that this IdP configuration was being added for the first time
on this server.
We have Dev, Test and Prod environments. The Dev version of the client's
IdP was working a couple of weeks ago, so I added the corresponding IdP
config in the Test environment today, after adding the
My application has a number of client organisations that want their users
to use their Active Directory through a SAML2 Identity Provider (IdP).
No problem, CAS supports this by being able to define multiple sets of
properties using cas.authn.pac4j.saml[0], cas.authn.pac4j.saml[1],
On Tuesday, August 28, 2018 at 10:39:43 AM UTC+2, leleuj wrote:
>
> Hi,
>
> The MFA features of the Apereo CAS server have a critical security
> vulnerability that allows one to bypass follow-up authentication factors.
>
> If your CAS deployment uses an MFA integration other than one with Duo
Hello Arnold.
I have write someting on UI custom here:
https://groups.google.com/a/apereo.org/forum/#!searchin/cas-user/customizing%7Csort:date/cas-user/yFUj7tAfwKo/ZD7IMHA-AQAJ
hope that will help you
Le lundi 27 août 2018 09:41:08 UTC+2, Bergner, Arnold a écrit :
>
> Hi all,
>
>
>
> I’m
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
