-
Notifications
You must be signed in to change notification settings - Fork 113
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
Grant Type Password Requires a client_id #71
Comments
@Niltz thanks, can you give some more details on the errors you're seeing? I'm not sure if this is related to this change, as it seems that's the only file where we deal with |
@toupeira The issue seems to be in the code to get the
|
I'm running exactly into this issue. Is this still being maintained ? |
@natashad thanks for looking into this! Still not sure how we should fix this though, according to the spec the
But looking at this article it seems it's also acceptable to return the username sent by the client as Unfortunately AFAICT we don't have access to that in Doorkeeper, since the user has to implement I wonder if it's also okay to return
@alduro barely, it's mostly just me ;-) Any help is welcome! |
The problem with the |
As per doorkeeper-gem/doorkeeper#296, client_id is optional for the password grant type, however doorkeeper-openid_connect seems to assume that it will always be there.
The text was updated successfully, but these errors were encountered: