You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We noticed unexpected behavior after updating django-oidc-provider0.7 to 0.8 when using standard and custom claims when forging the id_token.
When we define a resolver for custom claims using OIDC_EXTRA_SCOPE_CLAIMS, the OIDC_USERINFO is somehow ignored.
After some research, we discovered that this behavior was introduced by this commit (64e395c) and from what I understood from reading the code, StandardScopeClaims are never called when OIDC_EXTRA_SCOPE_CLAIMS is defined.
So my questions is,
Is this normal behavior? (I have some doubts about this after reading the commit message and the corresponding documentation).
Hi @bmihelac! We ended up doing the same thing by forking and patching the package on our end. Unfortunately, I can't share the exact fix since I'm no longer with that company 😅
Hi there!
We noticed unexpected behavior after updating
django-oidc-provider
0.7
to0.8
when using standard and custom claims when forging theid_token
.When we define a resolver for custom claims using
OIDC_EXTRA_SCOPE_CLAIMS
, theOIDC_USERINFO
is somehow ignored.After some research, we discovered that this behavior was introduced by this commit (64e395c) and from what I understood from reading the code,
StandardScopeClaims
are never called whenOIDC_EXTRA_SCOPE_CLAIMS
is defined.So my questions is,
The text was updated successfully, but these errors were encountered: