-
-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ENHANCE: Add "claims_supported" part of openid-configuration #332
Comments
https://github.com/juanifioren/django-oidc-provider/blob/master/oidc_provider/views.py#L260-L292 Doesn't look like there are currently any mechanisms to support this. It's not part of the current built in response, so would need to be added. Note |
Correct -- it is not required but I have run into a couple of large third party enterprise systems that are treating it as if it were required (not adhering to standards). In any case, it might be a "nice-to-have" for future revisions of the library. Thanks for the reply! |
You bet - does sound like it would be a useful feature to have. Might be worth re-opening this issue or create a new request as an enhancement if you're interested! |
Can I just use an issue as an enhancement? Didn't know what was polite way to do it. I'll reopen and see what we get. |
yup! You may want to rename it so it's more indicative of the request - something like: At some point a maintainer can tag the issue as an Enhancement (See labels tab in the Issues section). |
Forgive the perhaps obvious question -- trying to interface a working OIDC provider setup with a third-party system that is complaining that the "claims_supported" dictionary is not provided at .well-known/openid-configuration
How do we enable that section? I'm a bit lost in the weeds of the documentation. I don't want to create any custom types, just the standard ones. I was told by this third party that our openid-configuration should look similar to this demo response:
https://abc123-admin.oktapreview.com/.well-known/openid-configuration
The text was updated successfully, but these errors were encountered: