[13.x] Support Token Revocation RFC7009 and Token Introspection RFC7662 #1858
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.
Token Revocation
Token Revocation RFC7009
First, enable the token revocation by calling the
Passport::enableTokenRevocationmethod in the boot method of your application'sApp\Providers\AppServiceProviderclass:Passport::enableTokenRevocation();Then, the consuming application should make a
POSTrequest to your application's/oauth/revokeroute:This will return an empty
200response.Token Introspection
Token Introspection RFC7662
First, enable the token introspection by calling the
Passport::enableTokenIntrospectionmethod in the boot method of your application'sApp\Providers\AppServiceProviderclass:Passport::enableTokenIntrospection();Then, the consuming application should make a
POSTrequest to your application's/oauth/introspectroute:This will return a JSON response containing
activeattribute that indicates whether or not the presented token is currently active.