Hi,
In 5.0.0, many things have changed and I think it will be a global move.
To generate specific access tokens, you now have
a
https://github.com/apereo/cas/blob/master/support/cas-server-support-oauth/src/main/java/org/apereo/cas/support/oauth/web/OAuth20AccessTokenResponseGenerator.java
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 ot
Hi,
You can log in at Azure or Google via the authentication delegation
feature:
https://apereo.github.io/cas/6.0.x/configuration/Configuration-Properties.html#openid-connect-1
Choosing the OpenID Connect provider per service is a customization.
Thanks.
Best regards,
Jéôme
Le mardi 22
Hi,
This change was tested and works in pac4j applications. The issue in CAS is
that there are conflicts regarding the Nimbus versions libraries.
Add this to make it work:
com.nimbusds
nimbus-jose-jwt
6.0.2
com.nimbusds
oauth2-oidc-sdk
6.5
Thanks.
Best regards,
Hi,
The pac4j v3.6.1 release has been cut and the 5.3.x, 6.0.x and master
branches of CAS have been upgraded.
Thanks.
Best regards,
Jérôme
Le vendredi 15 février 2019 08:46:45 UTC+1, Andy Ng a écrit :
>
> Hi Jérôme
>
> > That said, as CAS v5.3.9 and v6.0.2 releases are planned for March 01,
>
Hi,
You have the following property/option: *cas.tgc.pinToSession* (true by
default) to attach the IP and user-agent to the SSO session.
In most cases, it's the right choice, but you may want to disable that
behavior.
Thanks.
Best regards,
Jérôme
Le mardi 28 janvier 2020 11:46:57 UTC+1, Andy
