Skip to content
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

password grant_type does not work #357

Closed
crystalneth opened this issue Feb 5, 2014 · 4 comments
Closed

password grant_type does not work #357

crystalneth opened this issue Feb 5, 2014 · 4 comments

Comments

@crystalneth
Copy link

Password grant_type is both a token and an authorization method, but it's managed by the token controller which does not run the authorization step. Therefore it does not authorize the user with the provided username and password.

@kennuzzo
Copy link

I have the same issue as well, i get a token with curl but is not usable

@wedtm
Copy link

wedtm commented Mar 25, 2014

I have found that you have to pass both the client_id and client_secret when doing a password grant.

@jagthedrummer
Copy link

Is this still an issue? I just looked into #382, which is related, and I think that it's possible to do the password credentials flow without client_id or client_secret. I saw that there's already a test for issuing a token without the client credentials, so I tried to write test for using the token that's issued.

https://github.com/jagthedrummer/doorkeeper/blob/jeremy/issue-382-password-grant/spec/requests/flows/password_spec.rb#L52-L61

The test passes using the issued token, but it fails with any other token. Let me know if I'm missing something there.

@tute
Copy link
Contributor

tute commented May 2, 2014

Closing after comment from @jagthedrummer (thank you!) and in #382. If it continues to be a problem, please provide reproducible steps and we'll address!

@tute tute closed this as completed May 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants