; Hi,
>
> You are missing nothing. pac4j authentication attributes are not used to
> build the CAS principal, only the user attributes.
> Thanks.
> Best regards,
> Jérôme
>
>
>
> On Tue, Nov 13, 2018 at 3:48 PM David Oteo >
> wrote:
>
>> Hi,
>&g
Hi,
We configured CAS 5.2.2 to delegate authentication to an external IdP
through SAML. In the SAML response there is an "AuthnContext" tag that does
not appear in the user profile attributes. CAS 5.2.2 seems to use pac4j
v2.2.x and here (https://github.com/pac4j/pac4j/pull/961) I can see that
uld be the version 5.3.x, given the fact the profileId
> could be set by properties (it's an easy improvement though).
>
> Thanks.
> Best regards,
> Jérôme
>
>
> On Thu, Nov 8, 2018 at 2:18 PM David Oteo >
> wrote:
>
>> Hello,
>>
>> We succesfully
Hello,
We succesfully configured CAS 5.2.2 to delegate authentication to an
external provider through generic OAuth2 properties:
#(Optional) Friendly name for OAuth 2 provider, e.g. "This Organization" or
"That Organization"
cas.authn.pac4j.oauth2[0].clientName=Giltza Oauth 2