I haven't tried v6.4.6, but the same problem does still occur with v6.5.0.
On Sat, Mar 5, 2022, 11:22 PM Stef wrote:
> Hi,
>
> Do you know if this problem has been solved in 6.4.6 ?
>
> Stéphane
>
> Le lun. 31 janv. 2022, 09:22, Rodolphe Prin a
> écrit :
>
>> Hi,
>> I noticed the same
Hi,
Do you know if this problem has been solved in 6.4.6 ?
Stéphane
Le lun. 31 janv. 2022, 09:22, Rodolphe Prin a
écrit :
> Hi,
> I noticed the same behavior.
> Version : 6.4.4.2
>
> `cas.authn.oidc.core.include-id-token-claims=true` allows to get the
> claims in the token, but with the
Hi,
I noticed the same behavior.
Version : 6.4.4.2
`cas.authn.oidc.core.include-id-token-claims=true` allows to get the
claims in the token, but with the wrong name.
Rodolphe
Le mardi 11 janvier 2022 à 20:01:46 UTC+1, John Wagenleitner a écrit :
> Hi Frédéric,
>
> Thanks for the reply. In
Hi Frédéric,
Thanks for the reply. In our case the claims are being included in the ID
Token, they just don't have the names we mapped and instead have the names
as they come from our attribute store. We are using `respone_type=code` and
a `scope=openid`.
I had not tried
Hello,
Have you tried to set cas.authn.oidc.core.include-id-token-claims=true ?
According to OIDC spec, if you are using response-type=code , the id_token
should not contain the user claims. But, if you are using
response_type=id_token, then the id_token should include the user claims.
According
In CAS v6.3 (up to and including v6.3.7.4) we used the
`cas.authn.oidc.claims-map` properties to map our LDAP attribute names to
the standard claim names. This mapping worked for both the ID Token and the
UserInfo (`/profile`) endpoint.
Here are the relevant properties we have set:
```
