-
Notifications
You must be signed in to change notification settings - Fork 41
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
Issue with Google oAuth #164
Comments
Are you using Redis based sessions like documented here? |
No :( Will that fix it? I have redis working for persisting events. Can I share the same instance? |
Probably yes. And yes. |
Okay. Rolling it out now :D Thanks @daffl |
Works like a dream now <3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
I'm seeing some inconsistent behavior with google oauth using feathers-sync.
Occasionally seeing the following error:
I'm wondering if the api for some reason start oauth in one instance and then redirects back to another instance?
Perhaps I need to also configure feathers http endpoint for sticky sessions to avoid any issues there?
The text was updated successfully, but these errors were encountered: