Added client credentials grant + implemented token revocation #11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ion in Guzzle (for example 503 HTTP code returned)
fminov
changed the title
… oauth2-server-laravel's postAccessToken responses)
thinkingmik
added a commit
that referenced
this pull request
Jul 4, 2015
Added client credentials grant + implemented token revocation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
This PR includes :
a simple modification to enable client_credentials grant with the API proxy
a bugfix for Guzzle not to fail on ServerExecption but proxy the error back to the caller
an implementation of token revocation, base on https://tools.ietf.org/html/draft-ietf-oauth-revocation-11 (I implemented it in lucadegasperi/oauth2-server-laravel and it needed this new proxy feature)