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

sign in Refresh token after redirect not match in table refresh_tokens #520

Open
chanthavong opened this issue May 20, 2024 · 3 comments
Open

Comments

@chanthavong
Copy link

No description provided.

@dbarrosop
Copy link
Contributor

Please, would you mind elaborating a bit? Thanks!

@chanthavong
Copy link
Author

example

  1. https://auth.xxx.com/signin/provider/google/callback
  2. https://front.xxx.com?refreshToken=1xxxx-xxxxxx-xxxxxx-xxxxx

but go to find 1xxxx-xxxxxx-xxxxxx-xxxxx in table refresh_token not have data

Result Error 401

(i use nhost sdk) : NhostClient

help me please 🙏. @dbarrosop

@dbarrosop
Copy link
Contributor

dbarrosop commented May 20, 2024

Are you self-hosting? In the case make sure you understand this document:

https://github.com/nhost/hasura-auth/blob/main/docs/workflows/oauth-providers.md

I suspect your callback configuration is wrong on google's side, it should point to the Auth service, not the application.

If you are using our cloud refer to our docs: https://docs.nhost.io/guides/auth/social/sign-in-google.

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

2 participants