-
Notifications
You must be signed in to change notification settings - Fork 784
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
Bypass auth screen if we already have a token #16
Comments
Same question.. |
@taylorotwell can you take a look at this issue ? This seems problematic when an app it's depending only on oAuth server to authenticate users. And it's annoying to ask each time the user to authorize (even if previously has approved the request). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unless the token has expired, the consumer has explicitly requested re-auth or the scopes have changed, we shouldn't need to continue showing the auth screen.
The text was updated successfully, but these errors were encountered: