-
Notifications
You must be signed in to change notification settings - Fork 5
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
Staging deploy uses production client ID for auth #199
Comments
Looked into this a little, still can't figure out why |
I'm guessing the |
Maybe a separate staging config needs to be defined? Seems like this should work though. Perhaps later webpack versions broke this kind of setup. |
Noting zooniverse/classroom#174 is indeed same issue. |
Staging deploy uses production client ID for auth instead of staging client ID. I've updated production Doorkeeper so staging deploy allows sign-in (to production, not what desired which would be to staging API) until resolved.
The text was updated successfully, but these errors were encountered: