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

Validate token #641

Closed
nrwiersma opened this issue Aug 18, 2016 · 3 comments
Closed

Validate token #641

nrwiersma opened this issue Aug 18, 2016 · 3 comments

Comments

@nrwiersma
Copy link

Hi,

Was looking for a way to manually validate a token. It seems to only be possible to through a bearer token validator. There are a fair number use cases for this, the main one in my case is allowing consumers to validate a token and its scopes.

As a reference, GitHub does this, the documentation can be found here.

@alexbilbie
Copy link
Contributor

You'll need to implement this manually for now, but V6 will support "token
introspection" which is an RFC that I've been working on.

On 18 August 2016 at 20:25:46, Nicholas Wiersma ([email protected])
wrote:

Hi,

Was looking for a way to manually validate a token. It seems to only be
possible to through a bearer token validator. There are a fair number use
cases for this, the main one in my case is allowing consumers to validate a
token and its scopes.

As a reference, GitHub does this, the documentation can be found here
https://developer.github.com/v3/oauth_authorizations/#check-an-authorization
.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#641, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAEwp7xfhksLtwuixXsesPgsFjrTSkBAks5qhLG6gaJpZM4Jn1CI
.

@nrwiersma
Copy link
Author

Awesome, great to hear. Thanks.

@simonhamp
Copy link

@alexbilbie did Introspection make it's way into v6?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants