Q: Google OAuth 2 Error 400: redirect_uri_mismatch but redirect uri is compliant and already registe-CodePudding

I am developing a NextJS application using next-auth with Google Oauth 2 as its authentication provider. The production build is running on Heroku. When attempting to sign in on my production build, Google OAuth is giving me "Error 400: redirect_uri_mismatch". Normally this would be an easy fix, except the exact uri is already registered in Cloud Console.

See my cloud console config .

I have also tried added many different permutations of my uri, but this did not help.

This issue not solved by 11485271 or 69151061.

Error in question:

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.

Request Details If you’re the app developer, make sure that these request details comply with Google policies. redirect_uri: https://middcourses2.herokuapp.com/api/auth/callback/google

Image of error page

And here is a link to the list of authorized domains in GCP.

CodePudding user response：

Solved! So for some reason, Google changed my Client ID and Client Secret after I already set up those env variables. Once I noticed the change and inputted the new values it worked fine.