-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Refresh token should be used in re-authorization flow (Gemini) #10978
Labels
Milestone
Comments
32 tasks
ryanml
added a commit
to brave/brave-core
that referenced
this issue
Jul 29, 2020
4 tasks
This was referenced Aug 21, 2020
Verification passed on
Verification passed on
Verification passed on
|
changing to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Currently, in the case of an invalid access token, the user presented with a message notifying them of the invalidity, and prompting them to re-connect. The
refresh_token
retrieved when creating the access token should be used it becomes invalid to retrieve another one. The re-connect messaging should only be shown in cases where the refresh action could not be achieved.Test Plan:
Within the console from the NTP. You should see it return
true
, and can confirm the new token works appropriately by updating balance or performing a trade.The text was updated successfully, but these errors were encountered: