Supabase Auth configuration supports passkeys and WebAuthn
Introduced 2026-04-27 · score 0.97
HOW TO USE IT
When enabling passkey authentication, add `[auth.passkey]` and `[auth.webauthn]` to `supabase/config.toml`; set `enabled = true` and provide the relying-party display name, ID, and origins.
[auth.passkey]
enabled = true
[auth.webauthn]
rp_display_name = "<app name>"
rp_id = "<bare domain, e.g. example.com>"
rp_origins = ["<https://app.example.com>"]WHY THIS HELPS
Configure passkeys and WebAuthn for a Supabase Auth project.
REQUIREMENTS AND LIMITATIONS
- Version: v2.95.4
- auth.passkey.enabled (required): Enable passkey sign-in and registration; requires `auth.webauthn` configuration.
- auth.webauthn.rp_display_name (required): Human-readable relying-party name shown during passkey ceremonies.
- auth.webauthn.rp_id (required): Relying-party identifier; must be a registrable suffix of every configured origin.
- auth.webauthn.rp_origins (required): List of app origins allowed for WebAuthn ceremonies.
- Prerequisite: Include `[auth.webauthn]` with all three relying-party values when `auth.passkey.enabled` is true.
- Prerequisite: Origins must use HTTPS except loopback addresses; each origin hostname must match or be a subdomain of the relying-party ID. Up to five origins are allowed.
FIRST-PARTY EVIDENCE
- https://github.com/supabase/cli/releases/tag/v2.95.4
- https://supabase.com/docs/guides/auth/passkeys
- https://supabase.com/docs/guides/local-development/cli/config
Check the installed version and the source before using it. Entry JSON