-
Notifications
You must be signed in to change notification settings - Fork 60
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
OAuth flow with assembly loading #3194
Comments
andrzejgrzelak
pushed a commit
to andrzejgrzelak/jbrowse-components
that referenced
this issue
Jan 18, 2023
…does help when there was a token present but refresh token was not found.
garrettjstevens
pushed a commit
that referenced
this issue
Mar 13, 2023
… help when there was a token present but refresh token was not found.
cmdcolin
added a commit
that referenced
this issue
Jun 7, 2023
…h flows (#3572) * Workaround of #3194, when not in web worker. Now refreshing page does help when there was a token present but refresh token was not found. * Make refresh token not found message more clear. * Remove jwt-decode from OAuth validateToken Tokens are not guaranteed to be JWT, so instead validate with a HEAD request * OAuth flow improvements * Add OAuth and HTTP BasicAuth servers for local testing (#3742) * Only mutate the loc.preauth info if not using MainThreadRpcDriver * Move files around, add http basic auth test * Use published version of @node-oauth/express-oauth-server --------- Co-authored-by: grzelaka <andrzej.grzelak@contractors.roche.com> Co-authored-by: Colin <colin.diesh@gmail.com>
I think after latest work on oauth this can be closed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, there still could be an issue if user:
This may result in an error, but now refreshing the page after this error at least will request a new token.
Originally posted by @andrzejgrzelak in #3175 (comment)
The text was updated successfully, but these errors were encountered: