-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
redirect_uri_mismatch after update from 0.1.34 to 0.1.37 #420
Comments
Looks to be possibly a breaking change with omniauth-oauth2 in 1.4.0. See also -- omniauth/omniauth-oauth2#82 Could you check your omniauth-oauth2 gem version? We may need to pin to a last known stable, etc. |
I had 1.4.0, when i rollback to 1.3.1 all works fine :) Also works fine on 1.4.0 when i apply this commit - zquestz/omniauth-google-oauth2#205 |
Where are 1.4.0 version? I see only 1.3.7beta3 |
1.4.0 version of omniauth-oauth2 gem. |
+1 |
Sounds like we have a solution to this problem and no activity in almost 2 years. Closing for now. |
After update from version 0.1.34 to 0.1.37 i have redirect_uri_mismatch error in google (facebook work fine). I didn't change any other data.
Google msg:
"The redirect URI in the request: https://xxx.com/api/omniauth/google_oauth2/callback?auth_origin_url=https%3A%2F%2Fxxx.com%2F%23%2Fsignin&omniauth_window_type=sameWindow&resource_class=User did not match a registered redirect URI."
Redirect URI in google console:
https://xxx.com/api/omniauth/google_oauth2/callback
Maybe it's problem with uri encode?
The text was updated successfully, but these errors were encountered: