-
Notifications
You must be signed in to change notification settings - Fork 368
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
Response type "none" seems to not be supported #409
Comments
Do you have an actual use case for this? |
One is described in the spec:
I am in fact working on a system which is similar, just that it provides access to datasets, but which might not yet have been uploaded. |
Ok, contributions welcome! |
I am closing this issue as it has not received any engagement from the community or maintainers in a long time. That does not imply that the issue has no merit. If you feel strongly about this issue
We are cleaning up issues every now and then, primarily to keep the 4000+ issues in our backlog in check and to prevent maintainer burnout. Burnout in open source maintainership is a widespread and serious issue. It can lead to severe personal and health issues as well as enabling catastrophic attack vectors. Thank you to anyone who participated in the issue! 🙏✌️ |
Is your feature request related to a problem? Please describe.
It seems the edge case response type "none" is not implemented/supported? I checked that by looking at the code. Nor I have found any test trying to test for this case.
Describe the solution you'd like
That support for "none" response type is implemented.
Additional context
Spec: https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html#none
The text was updated successfully, but these errors were encountered: