User profile data overrides id token claims about angular-oauth2-oidc HOT 4 CLOSED

Thx for this info. In the current version I did this on purpose, cause when it comes to the password flow there isn't a id_token and I assumed that in most cases the claims in the id_token are a subset of the claims from the user-profile-endpoint.

Isn't this true in your case?
To provide an uniform way to access the claims, would it work for you if the claims from the user-profile-endpoint and the claims from the id_token would be merged?

from angular-oauth2-oidc.

This is a thing, as i understood from here ID token doesn't have user's claims. In order to get user info i need to call UserInfo Endpoint. At least my identity server doesn't include user's claims into id token.

from angular-oauth2-oidc.

FWIW id tokens can have user claims. Our idp does include some minimal user clams (profile related) in the id token.

from angular-oauth2-oidc.

The next version which lands in a few days will merge the received claims with existing claims (from the id_token).

from angular-oauth2-oidc.