-
Notifications
You must be signed in to change notification settings - Fork 146
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
Client credentials grant #48
base: master
Are you sure you want to change the base?
Conversation
+1 to merging this pull request. |
+1 |
7 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
So far a lot of people have +1-ed this and no-one has described their use case. In the past I've been very reluctant to add in anything beyond the draft-10 spec since this creates a hybrid implementation that doesn't accurately embody any particular spec. So, who has a use case? |
I use this to provide API access to clients without a user authorization. I have some API calls that don't require a user's authorization, and it's easier to just keep everything within the OAuth context. |
This is indeed interesting to let the owner of a Client to authenticate and do some administrative task on, for example, Client configuration. |
http://tools.ietf.org/html/draft-ietf-oauth-v2-22#section-4.4