Google sign in fails with a redirect URI mismatch
We are seeing a redirect URI mismatch error when a customer tries Google sign in on our custom domain.
We are seeing a redirect URI mismatch error when a customer tries Google sign in on our custom domain.
Custom domains need their own callback URL added to the OAuth client authorized redirect URIs, the default subdomain one does not cover it automatically. Send us the domain and we will add it.
Custom domains need their own callback URL added to the OAuth client authorized redirect URIs, the default subdomain one does not cover it automatically. Send us the domain and we will add it.
Ran into this too, took about a day after asking support to add ours before it started working.
Took about a day for ours to get added too, matches what is described above.
Does this need to be redone if we rotate our OAuth client secret later?
No, redirect URIs are separate from the client secret, rotating the secret alone will not affect this.
Ours got added within a few hours actually, seems to depend on how busy support is that day.
Sign in to reply to this question.