Supabase OAuth provider setup: both consoles must agree or sign-in fails

TL;DR

Add your app's post-login redirect to Supabase's Redirect URLs allowlist (see the redirect-URL skill). TL;DR: TL;DR: Agents set up the Supabase provider toggle with a client ID and secret, then wonder why Google or GitHub rejects the flow: the provider never heard of the redirect back to Supabase. ## Checkable procedure 1. # Supabase OAuth: configure both consoles, not one OAuth is a handshake between two dashboards.

TL;DR: TL;DR: Agents set up the Supabase provider toggle with a client ID and secret, then wonder why Google or GitHub rejects the flow: the provider never heard of the redirect back to Supabase. ## Checkable procedure 1. # Supabase OAuth: configure both consoles, not one OAuth is a handshake between two dashboards. In the provider console (Google Cloud, GitHub, etc.), create the OAuth client and register the authorized redirect URI.

TL;DR: Agents set up the Supabase provider toggle with a client ID and secret, then wonder why Google or GitHub rejects the flow: the provider never heard of the redirect back to Supabase. ## Checkable procedure 1. # Supabase OAuth: configure both consoles, not one OAuth is a handshake between two dashboards. In the provider console (Google Cloud, GitHub, etc.), create the OAuth client and register the authorized redirect URI.

Supabase OAuth provider setup: both consoles must agree or sign-in fails

Fix

1. Agents set up the Supabase provider toggle with a client ID and secret, then wonder why Google or GitHub rejects the flow: the provider never heard of the redirect back to Supabase. ## Checkable procedure 1. Expected: this specific failure stops.

2. Copy it from there so there is no typo. Expected: you have the value in hand.

3. In the Supabase dashboard, enable the provider and paste the client ID and client secret from the provider console. Expected: this specific failure stops.

4. Add your app's post-login redirect to Supabase's Redirect URLs allowlist (see the redirect-URL skill). Expected: this specific failure stops.

Details

Supabase OAuth: configure both consoles, not one OAuth is a handshake between two dashboards. In the provider console (Google Cloud, GitHub, etc.), create the OAuth client and register the authorized redirect URI. 2. 3. The provider callback and your app redirect are two different URLs and both must be registered in their respective places. 4. Request only the scopes you need. Extra scopes trigger extra consent screens and, on some providers, a verification review that blocks launch. 5. Test with a fresh account on the provider. Watch for the consent screen: wrong scopes show up there. If the provider errors before consent, the redirect URI in step 1 is wrong. If Supabase errors after consent, the client secret in step 2 is wrong.

When to use

You hit exactly this: Supabase OAuth provider setup: both consoles must agree or sign-in fails in Supabase OAuth provider setup.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Supabase OAuth provider setup.

Edge cases

• For Supabase this is your project's auth callback URL, shown in the dashboard provider settings under the callback field.
• Existing grants skip consent and hide scope problems. ## Quick test Complete OAuth with a brand-new provider account in incognito.

Verified against live Supabase docs 2026-09-26: https://supabase.com/docs/guides/auth/social-login