Google idp keep getting Error 400: redirect_uri_mismatch

Original message was deleted

Ask Inkeep•9/15/25, 3:53 PM

Hi @alka_99, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.

Ask Inkeep•9/15/25, 3:54 PM

Answer

For Google as an Identity Provider in ZITADEL, the redirect URI you must use is the one provided in the ZITADEL Console when configuring the Google provider template. You need to copy this exact ZITADEL Callback URL and register it as an Authorized redirect URI in your Google Cloud Console. If the redirect URI in the error does not match exactly (character for character) what is in your Google API Console, Google will show a redirect_uri_mismatch error. Double-check that there are no typos, extra spaces, or differences in protocol (https/http) , and that you are using the exact URL shown by ZITADEL in the Identity Provider configuration screen. If you have overwritten or customized settings per organization, ensure you are using the correct Callback URL for that context (1) .

Ask Inkeep•9/15/25, 3:54 PM

To learn more, see the sources I considered:

[1] Configure Google as an Identity Provider in ZITADEL

Ask Inkeep•9/15/25, 3:54 PM

Feel free to tag @Ask Inkeep with additional questions.

AAsk Inkeep To learn more, see the sources I considered: [[1] Configure Google as an Iden...

Ask InkeepAPP•9/15/25, 3:54 PM

Got it. Tagging @Rajat for additional help.

alka_99•9/15/25, 3:55 PM

@Ask Inkeep i already uses the redirect url that zitadel provided, but still having same error

Ask Inkeep•9/15/25, 3:55 PM

Thanks for the follow-up, @alka_99. I'll get back to you soon.

Ask Inkeep•9/15/25, 3:55 PM

Answer

If you are still getting a redirect URI error even after using the redirect URL provided by ZITADEL, the documentation highlights a few important checks:

The redirect URI you register in the Google Cloud Console must match the ZITADEL Callback URL exactly—character for character—including protocol (https) , domain, and path.
Double-check for any typos, spaces, or mismatches between the Google Console and what ZITADEL displays.
If you have organization-specific settings, make sure you are using the correct callback URL for that context.
By default, the callback URL takes the form:
```
https://<your-zitadel-domain>/idps/callback
```
```
https://<your-zitadel-domain>/idps/callback
```
This is what should be registered as the Authorized redirect URI in your Google project (1) .

If all values match and you still see the error, try:

Removing and re-adding the redirect URI in both ZITADEL and Google Cloud.
Using an incognito/private browser window to avoid cached login state.

For more details, see the official documentation: Configure Google as an Identity Provider in ZITADEL

Ask Inkeep•9/15/25, 3:55 PM

To learn more, see the sources I considered:

[1] Configure Google as an Identity Provider in ZITADEL

Ask Inkeep•9/15/25, 3:55 PM

Feel free to tag @Ask Inkeep with additional questions.

Ask Inkeep•9/15/25, 3:56 PM

Thanks for the follow-up, @alka_99. I'll get back to you soon.

Ask Inkeep•9/15/25, 3:56 PM

Answer

I wasn't able to find a direct answer, here are some relevant sources:

[Configure Google as an Identity Provider in ZITADEL][(2) ]:

Explains that you must use the exact ZITADEL Callback URL shown in your configuration as the Authorized redirect URI in Google Cloud, and describes key troubleshooting steps for redirect URI errors.

[How to use a custom OAuth callback URL for the external IdP][(7) ]:

Clarifies that ZITADEL uses built-in callback URLs for external IdPs and does not allow customizing the internal redirect URI; proxying may be required if you need a custom endpoint.

Ask Inkeep•9/15/25, 3:56 PM

Feel free to tag @Ask Inkeep with additional questions.

Rajat•9/16/25, 11:04 AM

hey @alka_99 welcome to the server and thanks for your querstion, I will look into it

alka_99•9/16/25, 12:14 PM

@Rajat right now it's working but the solution is the one that I mentioned above.

Maybe you should revise the docs or something

AAsk Inkeep To learn more, see the sources I considered: [[1] Configure Google as an Iden...

Ask InkeepAPP•9/17/25, 4:15 PM

Glad I could be helpful. Feel free to create a new thread with any new questions you may have.