-
Notifications
You must be signed in to change notification settings - Fork 301
Resource Owner Password Credentials Grant #21
Comments
Hi. |
OK I will try to implement that and send you a pull request. |
Ashihaby, |
gvanderploeg, |
BTW I have renamed UserPassCredentials Class to ClientCredentials, I think this name is better as you use it only for Client Authentication. |
Hi, How are you faring on this issue? It seems that commits for this issue were mixed into the same pull request as #32, so I did not include these in the merge. And by the way: please put the commits for this issue in a separate branch, without other commits. Otherwise the merge could probably get just as painful as the one for #32... |
Is there an update on this? I need this grant type as well so if it isn't ready yet I'll have to roll my own version. |
To me it looks like the feature is not complete (without the authenticator support), and there is no proper pull request (or a branch with only the correct commits). |
Thanks -- I figured since it had been 8 months since any progress it probably hadn't progressed, but wanted to confirm before I proceeded on my own. |
A note on PR #47 -- there is likely more work that could (and arguably should) be done on this. For starters the code which adds the resource owner to the auth server model could be moved into its own package (though I've had issues with splitting data models across packages in the past). Also, I didn't update the Selenium tests to add one for the new grant type and this should certainly be done. In fact I didn't run the Selenium tests at all yet, so I could have broken them. That said -- this appears to be working pretty well and I'm likely to go back to some other things for a bit. |
Hi all !! Thanks a lot to all the people involved in that project, it make things easier !! Cheers |
Hi,
Do you have a support for the grant type of password which was described in this section of the protocol http://tools.ietf.org/html/draft-ietf-oauth-v2-31#section-4.3 ?
The text was updated successfully, but these errors were encountered: