-
-
Notifications
You must be signed in to change notification settings - Fork 420
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
Question regarding refresh tokens documentation #290
Comments
@bhargavrpatel Have you found any solution to this? Could you let me know what you did with it? I too would be doing this and your question got me thinking. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
In the Refreshing tokens in OAuth2 document, the example stores the fetched token into the session, as shown below.
In a real application, this would be stores in some sort of a database. However, my question is this: How would you relate that token to a particular user that is not signed in?
Our problem is that we have a separate frontend and the API and every time a user visits the website, we do not really know who they are until they login. So, even if we store the token, we cannot really link it. So in our case, is it that we cannot use Refresh tokens at all? Is there anything identifiable in the
authorization_response
?Regards,
The text was updated successfully, but these errors were encountered: