Google oauth is not working with auth0 dev keys

Help
1

When trying to log into my app today for testing using a google account (and auth configured to use auth0’s dev keys), i am seeing the following error:

Screenshot_20220828_104854
Screenshot_20220828_104854619×842 45.3 KB

Error 400: redirect_uri_mismatch
You can’t sign in to this app because it doesn’t comply with Google’s OAuth 2.0 policy.
If you’re the app developer, register the redirect URI in the Google Cloud Console.

i even get this error using the “try connection” button when looking at the google oauth option in the social connections part of the auth0 dashboard

My initial impression is that this is something that I don’t have the ability to fix (besides providing my own keys for google Oauth). Is there a way to fix this that allows users to still do testing with auth0’s dev keys?

3 Likes
2

Getting same issue as of Aug 29

2 Likes
3

I got same error since AUG 27

1 Like
4

Try to add
Client ID and Client Secret from google in social connection page.

Get google Client ID and Client Secret
https://marketplace.auth0.com/integrations/google-social-connection

5

Hello everyone!

The issue with Dev Keys should be resolved now!

However, we recommend setting up your own keys, to avoid the limitations as per this article:

Thanks,
Art

1 Like
6

hi, i have an error with google login right now, i can’t login with a google account and i don’t get any errors, just does not login when i put all my data, and it shows the continue with google page again in an infinite loop

7

Hello, I’m still experiencing the same issue.

Screen Shot 2022-08-29 at 11.56.03 PM
Screen Shot 2022-08-29 at 11.56.03 PM2966×1604 218 KB

1 Like
8

Hi, still having the issue!!1
What could be the problem??

9

I followed the steps here to get a google client id and key and it’s finally working.

10

having same issue right now.

11

The same here right now.

12

This is possibly related to the Client IDs in social connections using the Auth0 keys for too long or breaching the development usage of said keys. Be good if the documentation as clearer or the error reporting of these occurrences we’re more user friendly here. Adding our own Client IDs from Google-auth control panel resolved the issue for us.