The “Error 400: redirect_uri_mismatch” error occurs when the redirect URI provided in the Google OAuth 2.0 authentication request does not match any of the authorized redirect URIs configured for your Google OAuth 2.0 Client ID.
To resolve this error, you need to ensure that the redirect URI used in your application matches one of the authorized redirect URIs in your Google OAuth 2.0 Client ID configuration. Here’s how you can fix it:
- Go to the Google Developers Console: https://console.developers.google.com/
- Select your project from the project dropdown in the top navigation bar.
- In the left sidebar, click on “APIs & Services” and then click on “Credentials”.
- Find the OAuth 2.0 Client ID you are using for your application and click on it to view its details.
- In the “Authorized redirect URIs” section, check if the redirect URI used in your application is listed. If not, you need to add it.
- To add a new redirect URI, click on the “ADD URI” button in the “Authorized redirect URIs” section.
- Enter the exact redirect URI that your application is using for the Google OAuth 2.0 authentication flow. This should match the URI where your application expects to receive the OAuth callback after successful authentication.
- Click on the “SAVE” button to save the changes.
- Update your application code to use the correct redirect URI that matches the one you added in the Google OAuth 2.0 Client ID configuration.
- Restart your application server for the changes to take effect.
After adding the correct redirect URI to your Google OAuth 2.0 Client ID configuration and updating your application code accordingly, the “redirect_uri_mismatch” error should be resolved, and the Google authentication should work as expected.
Make sure the redirect URI used in your application exactly matches the one configured in the Google Developers Console, including the protocol (http or https), domain, path, and any query parameters.
If you are using a library or framework for handling Google authentication, refer to its documentation to ensure you are configuring the redirect URI correctly within the library or framework settings.
Remember to update the redirect URI in both your development and production environments if they use different URLs.
If you continue to face issues, double-check the Google OAuth 2.0 Client ID and Client Secret you are using in your application, and ensure they are correctly set in your application’s configuration.