Open ArcRiiad opened 1 year ago
I have a similar issue. For now, as a workaround, I am subclassing from StandardScopeClaims:
-class CustomScopeClaims(ScopeClaims):
+class CustomScopeClaims(StandardScopeClaims):
@ArcRiiad did you ever find an answer?
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 (https://github.com/juanifioren/django-oidc-provider/commit/64e395c5b68b9374e6b3e1d1fedb362dacb9000d) and from what I understood from reading the code,
StandardScopeClaims
are never called whenOIDC_EXTRA_SCOPE_CLAIMS
is defined.So my questions is,