Skip to content

Supabase adds a backup sign-in path for OAuth-only accounts

Account Security now lets you set a fallback password and MFA recovery codes, so losing access to GitHub or ChatGPT sign-in no longer locks you out of your Supabase dashboard.

Source: Supabase

Supabase shipped two backup sign-in options for dashboard accounts on 13 November. If you signed up through GitHub, ChatGPT or another OAuth provider and never set a password, Account Security now lets you add one tied to your account email, so you can still get in if that provider is unreachable or you lose access to it.

The same update adds ten single-use MFA recovery codes alongside your authenticator app. If the app is lost or inaccessible, a code lets you complete MFA sign-in instead. The dashboard shows how many codes are left and lets you regenerate the set. Supabase says no action is required but recommends setting up both.

Why it matters: an OAuth-only account with no password and no recovery codes has one single point of failure for getting into your dashboard, which matters more once you’re managing production databases through it. Setting a backup password and generating recovery codes now, before you need them, is the point.

Account Security > Backup sign-in: set password, generate MFA recovery codes
Share

Related reading

More from The Wire

All briefs