A social login redirect fails with a redirect_uri error — how do I fix it?
- Topic
- Troubleshooting
- Asked by
- Developers configuring social login
redirect_uri_mismatch (and similar) errors come from the OAuth provider rejecting the callback URL because it doesn't exactly match what you registered in that provider's console.
Checklist:
Exact match. Scheme (
https), host, port and path must match character-for-character — including or excluding a trailing slash consistently.Use Atlas's callback URL. Copy the callback URL shown in the connection's settings in the Atlas dashboard and paste it into the provider's allowed redirect URIs. Don't hand-type it.
Custom domains. If you use a custom domain, register the callback for that domain, not the default one.
Credentials. Confirm the client ID/secret in Atlas match the provider app you registered the redirect on.
Atlas enforces exact-origin redirect checks and CSRF-bound state on its side, so also make sure you aren't tampering with the state parameter. See the connections/OAuth guide.
The redirect/callback URL registered with the social provider must exactly match the one Atlas uses, including scheme, host and path. A trailing-slash or http-vs-https mismatch is the most common cause.