-
Notifications
You must be signed in to change notification settings - Fork 984
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
Why can't we add bad providers ourself? #164
Comments
Refer to lengthy discussion about this topic here: |
Thanks, I missed that one! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm currently trying to implement a provider that did not follow the spec.
Currently the only way to get it working is by creating a fork and add it to the bad providers list.
The code tells me the following:
Why is this? I think there are many broken providers, is it really worth adding them all to the list by MR?
My suggestion is adding a
HasBrokenAuthHeader
field on theoauth2.Endpoint
type.Another option is adding a
AuthorizeLocation
field on theoauth2.Endpoint
type, the value could beheader
orquery
.The text was updated successfully, but these errors were encountered: