Nacho
Supabase Auth Fournisseur IAM
Open-source Postgres-native authentication backed by GoTrue. 50K MAU free tier, self-hostable on any infrastructure, and tightly integrated with the Supabase platform (database, storage, edge functions). Row Level Security is the authorization primitive.
Fonctionnalités
- 🇺🇸US🇪🇺EU🇦🇵AP🇨🇦CA🇸🇦SA
- AWSAzureGCPSelf-hosted
- JavaScriptTypeScriptReactNext.jsSvelteKitFlutterSwiftKotlinPython.NETGo
Si vous souhaitez comparer les fonctionnalités IAM de différents fournisseurs, consultez le benchmark des fournisseurs d'identité (C)IAM.
Vous cherchez la compatibilité au niveau du protocole OpenID Connect entre les fournisseurs ? Consultez le benchmark des fournisseurs OpenID Connect.
Foire aux questions
Supabase Auth prend-il en charge Nom d'utilisateur et mot de passe méthode d'authentification ?
Supabase Auth prend en charge Nom d'utilisateur et mot de passe méthode d'authentification. Email and password authentication available on all plans. Supports sign-up, sign-in, password reset via email, and email confirmation flows. Passwords stored as bcrypt hashes. Email enumeration protection is configurable. En savoir plus
Supabase Auth prend-il en charge Connexion sociale méthode d'authentification ?
Supabase Auth prend en charge Connexion sociale méthode d'authentification. 20 built-in OAuth providers: Google, Facebook, Apple, Azure/Microsoft, Twitter/X, GitHub, GitLab, Bitbucket, Discord, Figma, Kakao, Keycloak, LinkedIn, Notion, Slack, Spotify, Twitch, WorkOS, Zoom, and Fly.io. Additional custom OAuth2/OIDC providers configurable via the dashboard. En savoir plus
Supabase Auth prend-il en charge Passkey méthode d'authentification ?
Supabase Auth prend partiellement en charge Passkey méthode d'authentification. Passkeys (WebAuthn) are supported as an MFA factor for existing authenticated users, not as a standalone primary sign-in method. Users must first register with another method (email/password, magic link, etc.) before enrolling a passkey as a second factor. En savoir plus
Supabase Auth prend-il en charge Email Passwordless méthode d'authentification ?
Supabase Auth prend en charge Email Passwordless méthode d'authentification. Email OTP (6-digit one-time code) for passwordless sign-in. Rate limited to 30 OTPs per hour project-wide and 60-second window per user before a new OTP can be requested. Requires custom SMTP for production (built-in SMTP limited to 2 emails/hour). En savoir plus
Supabase Auth prend-il en charge Phone Passwordless méthode d'authentification ?
Supabase Auth prend en charge Phone Passwordless méthode d'authentification. Phone OTP via SMS for passwordless sign-in. Supports Twilio, Messagebird, Vonage, and custom SMS hooks. SMS costs are separate from Supabase billing. Requires a configured SMS provider. En savoir plus
Supabase Auth prend-il en charge Magic Link méthode d'authentification ?
Supabase Auth prend en charge Magic Link méthode d'authentification. Email magic link (one-time URL) for passwordless sign-in. Same rate limits as email OTP: 30 per hour project-wide, 60-second per-user cooldown. Requires custom SMTP for production use. En savoir plus
Supabase Auth prend-il en charge Anonymous / Guest méthode d'authentification ?
Supabase Auth prend en charge Anonymous / Guest méthode d'authentification. Anonymous sign-ins create a real user record in auth.users without credentials. Anonymous users can be converted to permanent accounts by linking an email, phone, or OAuth identity. Rate limited to 30 anonymous sign-ins per hour per IP address. Available on all plans. En savoir plus
Supabase Auth prend-il en charge Time-based One-Time Password (TOTP) MFA ?
Supabase Auth prend en charge Time-based One-Time Password (TOTP) MFA. TOTP (Time-based One-Time Password) MFA via authenticator apps (Google Authenticator, Authy, etc.). Free on all plans, enabled by default on every Supabase project. 30-second code validity with one-interval clock skew tolerance. Developers are responsible for building the enrollment and challenge UI. En savoir plus
Supabase Auth prend-il en charge HMAC-based One-Time Password (HOTP) MFA ?
Supabase Auth ne prend pas en charge HMAC-based One-Time Password (HOTP) MFA. Counter-based HOTP is not supported. Supabase MFA supports TOTP (time-based) and phone/passkey factors only. En savoir plus
Supabase Auth prend-il en charge Universal 2nd Factor (U2F) MFA ?
Supabase Auth prend en charge Universal 2nd Factor (U2F) MFA. Hardware security keys (YubiKey, etc.) supported as a WebAuthn MFA factor. Implemented via the same WebAuthn/passkey MFA API. Available on all plans. En savoir plus
Supabase Auth prend-il en charge WebAuthn MFA ?
Supabase Auth prend en charge WebAuthn MFA. WebAuthn/passkey MFA factor (Touch ID, Face ID, Windows Hello, hardware keys). Supported as an additional factor alongside TOTP. Users enroll via the Factor API. Available on all plans. En savoir plus
Supabase Auth prend-il en charge Email Code MFA ?
Supabase Auth ne prend pas en charge Email Code MFA. Email OTP is available as a primary authentication method but not as a dedicated MFA second factor. Supported MFA factors are TOTP, phone (SMS), and WebAuthn/passkeys. En savoir plus
Supabase Auth prend-il en charge Phone Code MFA ?
Supabase Auth prend partiellement en charge Phone Code MFA. Phone/SMS MFA available as a paid add-on: $75/month for the first project, $10/month per additional project. Not included in the base Pro or Team plan subscription. Requires a configured SMS provider (Twilio, etc.). En savoir plus
Supabase Auth prend-il en charge Recovery Code MFA ?
Supabase Auth ne prend pas en charge Recovery Code MFA. Recovery/backup codes are not supported. Supabase recommends enrolling multiple MFA factors (e.g., both TOTP and passkey) to prevent account lockout. En savoir plus
Supabase Auth prend-il en charge Push Notification MFA ?
Supabase Auth ne prend pas en charge Push Notification MFA. Push notification MFA is not supported natively. Can be approximated by integrating an external IdP (e.g., Okta, Duo) via SAML SSO. En savoir plus
Supabase Auth prend-il en charge Adaptive / Risk-Based MFA MFA ?
Supabase Auth ne prend pas en charge Adaptive / Risk-Based MFA MFA. Risk-based or adaptive MFA is not supported. MFA policy is all-or-nothing (require MFA for all users or none). Can be partially implemented via the MFA Verification Attempt hook. En savoir plus
Supabase Auth prend-il en charge Cisco Duo MFA ?
Supabase Auth ne prend pas en charge Cisco Duo MFA. No native Cisco Duo integration. Duo can be reached indirectly by configuring Duo as a SAML IdP via Enterprise SSO (Pro+ plan). En savoir plus
Supabase Auth prend-il en charge Step-Up Authentication MFA ?
Supabase Auth prend en charge Step-Up Authentication MFA. Step-up authentication via Authenticator Assurance Level (AAL) checks. Routes users through MFA verification when accessing sensitive resources by inspecting the `aal` claim in the session JWT. Available on all plans. En savoir plus
Supabase Auth prend-il en charge OpenID Connect (OIDC) protocole d'intégration ?
Supabase Auth prend en charge OpenID Connect (OIDC) protocole d'intégration. Supabase Auth issues JWTs compliant with OpenID Connect. The auth server exposes JWKS endpoints for token verification. Acts as an OIDC provider for downstream services and supports OIDC-based social login. En savoir plus
Supabase Auth prend-il en charge SAML 2.0 protocole d'intégration ?
Supabase Auth prend en charge SAML 2.0 protocole d'intégration. SAML 2.0 Single Sign-On available on Pro plan and above. Priced at $0.015 per SSO MAU with 50 SSO MAU included per project. Works with any SAML 2.0-compatible IdP (Google Workspace, Okta, Auth0, Microsoft Entra ID, PingIdentity, OneLogin, etc.). En savoir plus
Supabase Auth prend-il en charge WS-Federation protocole d'intégration ?
Supabase Auth ne prend pas en charge WS-Federation protocole d'intégration. WS-Federation is not supported. Supabase Auth supports OIDC and SAML 2.0 as federation protocols. En savoir plus
Supabase Auth prend-il en charge Machine-to-Machine (M2M) Authentication protocole d'intégration ?
Supabase Auth prend en charge Machine-to-Machine (M2M) Authentication protocole d'intégration. OAuth 2.1 authorization server available for M2M and MCP (Model Context Protocol) auth flows. Service role keys provide admin-level API access for backend services. Anonymous tokens can also serve lightweight M2M patterns. En savoir plus
Supabase Auth prend-il en charge OpenID Connect (OIDC) Federation fédération d'identité ?
Supabase Auth ne prend pas en charge OpenID Connect (OIDC) Federation fédération d'identité. Supabase Auth does not support configuring external OIDC providers as enterprise IdP connections for SSO federation. Only SAML 2.0 is supported for enterprise SSO. Custom OAuth2/OIDC providers can be added for social login but not for federated enterprise identity. En savoir plus
Supabase Auth prend-il en charge SAML 2.0 Federation fédération d'identité ?
Supabase Auth prend en charge SAML 2.0 Federation fédération d'identité. SAML 2.0 enterprise identity federation. Supabase acts as the Service Provider (SP). Any SAML 2.0-compatible IdP is supported. Attribute mapping for user metadata configurable. Priced at $0.015/SSO MAU (50 included). En savoir plus
Supabase Auth prend-il en charge Active Directory / LDAP fédération d'identité ?
Supabase Auth ne prend pas en charge Active Directory / LDAP fédération d'identité. No native LDAP/Active Directory connector. AD users can federate via SAML 2.0 (e.g., Microsoft Entra ID, ADFS as SAML IdP) on Pro+ plans. En savoir plus
Supabase Auth prend-il en charge Azure Active Directory (Entra ID) fédération d'identité ?
Supabase Auth prend en charge Azure Active Directory (Entra ID) fédération d'identité. Microsoft Entra ID (Azure AD) supported both as a social OAuth provider (Microsoft app) and as an enterprise SAML 2.0 IdP (Pro+ plans). Full attribute mapping available via the SAML SSO configuration. En savoir plus
Supabase Auth prend-il en charge Bulk User Import gestion des utilisateurs ?
Supabase Auth prend en charge Bulk User Import gestion des utilisateurs. Bulk user import via the Admin API (createUser per user) or directly via SQL INSERT into auth.users. No native bulk import endpoint — large migrations require scripted API calls or direct database operations. Available on all plans. En savoir plus
Supabase Auth prend-il en charge Password Hash Import (Multiple Formats) gestion des utilisateurs ?
Supabase Auth prend partiellement en charge Password Hash Import (Multiple Formats) gestion des utilisateurs. Password hash import supported for bcrypt and scrypt formats via direct database operations. Limited documentation on supported hash algorithms. Firebase scrypt is specifically documented as importable. MD5, SHA, Argon2 not natively supported without custom migration scripts. En savoir plus
Supabase Auth prend-il en charge Bulk User Export gestion des utilisateurs ?
Supabase Auth prend en charge Bulk User Export gestion des utilisateurs. Users can be exported by querying the auth.users and auth.identities tables via the SQL Editor (CSV export available). No dedicated REST endpoint for bulk export — requires direct database access. En savoir plus
Supabase Auth prend-il en charge Bulk User Update / Delete gestion des utilisateurs ?
Supabase Auth prend partiellement en charge Bulk User Update / Delete gestion des utilisateurs. Individual update and delete available via Admin API (updateUserById, deleteUser). No bulk update/delete endpoint — operations must be scripted. Direct SQL DELETE on auth.users also works for mass deletions. En savoir plus
Supabase Auth prend-il en charge Upsert on Import gestion des utilisateurs ?
Supabase Auth ne prend pas en charge Upsert on Import gestion des utilisateurs. No native upsert-on-import functionality. Importing a user whose email already exists will fail. Handle deduplication before importing or use direct SQL with ON CONFLICT clauses. En savoir plus
Supabase Auth prend-il en charge Legacy Username Import (Non-Allowed Characters) gestion des utilisateurs ?
Supabase Auth prend partiellement en charge Legacy Username Import (Non-Allowed Characters) gestion des utilisateurs. Supabase Auth uses email (not username) as the primary identifier. A username field can be stored in a custom public.profiles table or in raw_user_meta_data but requires application-level uniqueness enforcement. No built-in username authentication. En savoir plus
Supabase Auth prend-il en charge MFA Enrollment Import gestion des utilisateurs ?
Supabase Auth ne prend pas en charge MFA Enrollment Import gestion des utilisateurs. Importing pre-existing MFA enrollments (TOTP secrets, phone numbers for MFA) is not supported. Users must re-enroll in MFA after migration. En savoir plus
Supabase Auth prend-il en charge Inbound SCIM Provisioning gestion des utilisateurs ?
Supabase Auth ne prend pas en charge Inbound SCIM Provisioning gestion des utilisateurs. No SCIM 2.0 endpoint. User lifecycle management must use the Admin REST API directly or third-party bridges. SCIM is not on the public roadmap. En savoir plus
Supabase Auth prend-il en charge Outbound SCIM Provisioning gestion des utilisateurs ?
Supabase Auth ne prend pas en charge Outbound SCIM Provisioning gestion des utilisateurs. No outbound SCIM provisioning to downstream applications. En savoir plus
Supabase Auth prend-il en charge SCIM Groups Provisioning gestion des utilisateurs ?
Supabase Auth ne prend pas en charge SCIM Groups Provisioning gestion des utilisateurs. No group objects or SCIM group management. Groups must be implemented via custom tables and RLS policies in the public schema. En savoir plus
Supabase Auth prend-il en charge Just-In-Time (JIT) User Provisioning gestion des utilisateurs ?
Supabase Auth prend en charge Just-In-Time (JIT) User Provisioning gestion des utilisateurs. Just-in-time provisioning: users are automatically created in auth.users on first sign-in via social OAuth, magic link, or SAML SSO. The Before User Created Auth Hook can customize or block provisioning. En savoir plus
Supabase Auth prend-il en charge Lazy / Trickle Migration from Legacy Database gestion des utilisateurs ?
Supabase Auth prend partiellement en charge Lazy / Trickle Migration from Legacy Database gestion des utilisateurs. Lazy migration possible via the Password Verification Attempt Auth Hook, which can intercept failed local password checks and verify against a legacy system, then update the local hash on success. Requires Pro+ for Auth Hooks. No official zero-downtime migration tooling. En savoir plus
Supabase Auth prend-il en charge Self-Service Profile Management Portal gestion des utilisateurs ?
Supabase Auth prend partiellement en charge Self-Service Profile Management Portal gestion des utilisateurs. Users can update their own email, phone, password, and raw_user_meta_data via the client SDK. No built-in profile management UI — developers must build their own using the supabase-js SDK or @supabase/auth-ui-react components. En savoir plus
Supabase Auth prend-il en charge User Account Linking gestion des utilisateurs ?
Supabase Auth prend en charge User Account Linking gestion des utilisateurs. Multiple authentication providers (email, phone, OAuth) can be linked to a single user account. Anonymous users are automatically converted to permanent accounts when they link an identity. Manual linking via the linkIdentity API is supported. En savoir plus
Supabase Auth prend-il en charge User Blocking / Banning gestion des utilisateurs ?
Supabase Auth prend en charge User Blocking / Banning gestion des utilisateurs. Disable user accounts via the Admin API (updateUserById with banned_until set to a future date or '9999-12-31'). Blocked users cannot sign in. Ban can be time-limited or permanent. En savoir plus
Supabase Auth prend-il en charge User Metadata gestion des utilisateurs ?
Supabase Auth prend en charge User Metadata gestion des utilisateurs. User-editable metadata stored in raw_user_meta_data (JSONB column on auth.users). Updated via the client SDK (updateUser). No strict field schema — any JSON structure is accepted. Size is constrained by Postgres JSONB practical limits (not explicitly documented by Supabase). En savoir plus
Supabase Auth prend-il en charge Application Metadata gestion des utilisateurs ?
Supabase Auth prend en charge Application Metadata gestion des utilisateurs. Admin-only metadata stored in raw_app_meta_data (JSONB column). Cannot be updated by the client SDK — requires the service role key or Admin API. Used for storing authorization data like roles that should not be user-editable. En savoir plus
Supabase Auth prend-il en charge Metadata Size Limits gestion des utilisateurs ?
Supabase Auth prend partiellement en charge Metadata Size Limits gestion des utilisateurs. No explicit documented size limits on user_metadata or app_metadata fields. Both are stored as Postgres JSONB, so practical limits depend on the database row size and Postgres TOAST limits. Claims included in JWT access tokens are limited by typical JWT size constraints (should stay under 8 KB to avoid HTTP header issues). En savoir plus
Supabase Auth prend-il en charge User Search gestion des utilisateurs ?
Supabase Auth prend partiellement en charge User Search gestion des utilisateurs. Admin API provides listUsers with pagination (page, perPage) but no server-side search or filtering. To search by email, name, or metadata, query auth.users directly via SQL (requires service role access). No full-text search index on user fields. En savoir plus
Supabase Auth prend-il en charge Role-Based Access Control (RBAC) gestion des utilisateurs ?
Supabase Auth prend partiellement en charge Role-Based Access Control (RBAC) gestion des utilisateurs. No built-in RBAC system with a roles/permissions management UI. RBAC is implemented by storing role claims in raw_app_meta_data (via admin API) and enforcing them in Postgres RLS policies or application middleware. The Custom Access Token Hook can add role claims to JWTs. En savoir plus
Supabase Auth prend-il en charge Organizations (Multi-Tenancy B2B) gestion des utilisateurs ?
Supabase Auth ne prend pas en charge Organizations (Multi-Tenancy B2B) gestion des utilisateurs. No built-in organization or multi-tenancy model. Must be built manually using custom tables (organizations, memberships), RLS policies scoped by organization_id, and JWT claims. Each Supabase project is effectively a single tenant. En savoir plus
Supabase Auth prend-il en charge Password Strength Policies gestion des utilisateurs ?
Supabase Auth prend en charge Password Strength Policies gestion des utilisateurs. Password policy configurable in the Auth settings: minimum length, require uppercase/lowercase/numbers/special characters, and minimum password strength (using zxcvbn scoring). Leaked password protection (Have I Been Pwned integration) available on Pro+ plans. En savoir plus
Supabase Auth prend-il en charge Username Restrictions gestion des utilisateurs ?
Supabase Auth ne prend pas en charge Username Restrictions gestion des utilisateurs. Supabase Auth does not have a native username field with uniqueness constraints or format restrictions. The email field is the primary identifier. Username-based auth requires custom implementation (e.g., a unique username field in a public.profiles table with RLS). En savoir plus
Supabase Auth prend-il en charge Progressive Profiling / Forms gestion des utilisateurs ?
Supabase Auth ne prend pas en charge Progressive Profiling / Forms gestion des utilisateurs. No built-in progressive profiling flow. Custom progressive profiling can be implemented in the application layer using auth state and the updateUser API. En savoir plus
Supabase Auth prend-il en charge Attribute-Based Access Control (ABAC) contrôle d'accès ?
Supabase Auth prend en charge Attribute-Based Access Control (ABAC) contrôle d'accès. Row Level Security (RLS) policies provide fine-grained attribute-based access control at the Postgres level. Policies can reference user attributes from auth.uid() and auth.jwt() to filter rows. The combination of RLS + JWT claims implements a full ABAC model for database resources. En savoir plus
Supabase Auth prend-il en charge Fine-Grained Authorization (FGA / ReBAC) contrôle d'accès ?
Supabase Auth prend partiellement en charge Fine-Grained Authorization (FGA / ReBAC) contrôle d'accès. Row-level granularity via Postgres RLS — every SELECT/INSERT/UPDATE/DELETE can be controlled per-user per-row. However, no relationship-based access control (ReBAC) graph model. Complex sharing models (e.g., 'user A can edit document B because A is in group C which has editor access') require custom join logic in RLS policies. En savoir plus
Supabase Auth prend-il en charge API Authorization (Scopes / Permissions) contrôle d'accès ?
Supabase Auth prend en charge API Authorization (Scopes / Permissions) contrôle d'accès. Supabase auto-generates a REST and GraphQL (pg_graphql) API with RLS enforcement. JWT access tokens are validated on every request. Service role bypasses RLS for admin operations. OAuth scopes via the OIDC provider. En savoir plus
Supabase Auth prend-il en charge Audit Log Retention fonctionnalité de sécurité ?
Supabase Auth prend partiellement en charge Audit Log Retention fonctionnalité de sécurité. Auth events are logged in Postgres via the GoTrue server. On managed cloud, log retention is limited. Log Drains (paid add-on: $60/drain/month + usage) available on Pro+ for streaming to external SIEM/logging services. On self-hosted, log retention is infrastructure-managed. En savoir plus
Supabase Auth prend-il en charge Audit Log Streaming fonctionnalité de sécurité ?
Supabase Auth prend partiellement en charge Audit Log Streaming fonctionnalité de sécurité. Log Drains available on Pro+ as a paid add-on ($60/drain/month + $0.20/million events + $0.09/GB egress). Supports streaming to BigQuery, Datadog, Elastic, HTTPS endpoints. Auth events included. Not available on Free plan. En savoir plus
Supabase Auth prend-il en charge Security Center (Threat Monitoring Dashboard) fonctionnalité de sécurité ?
Supabase Auth ne prend pas en charge Security Center (Threat Monitoring Dashboard) fonctionnalité de sécurité. No dedicated security dashboard or threat intelligence center. Auth metrics available via the Supabase dashboard (sign-ins, errors) but no real-time security alerting. En savoir plus
Supabase Auth prend-il en charge Encryption at Rest fonctionnalité de sécurité ?
Supabase Auth prend en charge Encryption at Rest fonctionnalité de sécurité. AES-256 encryption at rest for all data and backups on Supabase Cloud. Self-hosted encryption depends on the underlying infrastructure provider. En savoir plus
Supabase Auth prend-il en charge Encryption in Transit fonctionnalité de sécurité ?
Supabase Auth prend en charge Encryption in Transit fonctionnalité de sécurité. All connections to Supabase APIs require TLS. HTTP connections are automatically redirected to HTTPS. Database connections use SSL/TLS by default. En savoir plus
Supabase Auth prend-il en charge Customer Managed Keys (BYOK) fonctionnalité de sécurité ?
Supabase Auth ne prend pas en charge Customer Managed Keys (BYOK) fonctionnalité de sécurité. Customer-managed encryption keys (CMEK) are not available. Encryption keys are managed by Supabase. En savoir plus
Supabase Auth prend-il en charge Bot Detection fonctionnalité de sécurité ?
Supabase Auth ne prend pas en charge Bot Detection fonctionnalité de sécurité. No native bot detection or CAPTCHA integration in Supabase Auth. Bot protection can be added at the application layer (e.g., Cloudflare Turnstile, hCaptcha) before calling Supabase Auth APIs. En savoir plus
Supabase Auth prend-il en charge Brute Force Protection fonctionnalité de sécurité ?
Supabase Auth prend en charge Brute Force Protection fonctionnalité de sécurité. Built-in rate limiting on all auth endpoints (e.g., 360 verify requests/hour by IP, 1800 token refreshes/hour by IP). Anomalous refresh token reuse detected and triggers session revocation. Some limits are configurable via the dashboard. En savoir plus
Supabase Auth prend-il en charge Suspicious IP Throttling fonctionnalité de sécurité ?
Supabase Auth prend partiellement en charge Suspicious IP Throttling fonctionnalité de sécurité. Auth API rate limits are enforced per IP address (e.g., anonymous sign-ins: 30/hour per IP; OTP: 30/hour project-wide). No dedicated suspicious-IP detection or block-list management. Cloudflare DDoS mitigation applies at the infrastructure level. En savoir plus
Supabase Auth prend-il en charge Breached Password Detection fonctionnalité de sécurité ?
Supabase Auth prend partiellement en charge Breached Password Detection fonctionnalité de sécurité. Leaked password protection available on Pro+ plans. Checks passwords against the Have I Been Pwned database during sign-up and password changes. Not available on Free plan. En savoir plus
Supabase Auth prend-il en charge Credential Guard (Dark Web Monitoring) fonctionnalité de sécurité ?
Supabase Auth ne prend pas en charge Credential Guard (Dark Web Monitoring) fonctionnalité de sécurité. No proactive continuous monitoring for compromised credentials beyond the standard leaked password protection check at sign-up/password-change. En savoir plus
Supabase Auth prend-il en charge Tenant Access Control List (IP ACL) fonctionnalité de sécurité ?
Supabase Auth ne prend pas en charge Tenant Access Control List (IP ACL) fonctionnalité de sécurité. No tenant-level access control lists for restricting sign-in traffic by IP, geography, or other signals. IP filtering must be applied at the infrastructure or reverse proxy layer. En savoir plus
Supabase Auth prend-il en charge Device Fingerprinting fonctionnalité de sécurité ?
Supabase Auth ne prend pas en charge Device Fingerprinting fonctionnalité de sécurité. No native device fingerprinting. Sessions track a session_id in the JWT but do not fingerprint the device. Can be added at the application layer via third-party services. En savoir plus
Supabase Auth prend-il en charge Per-Organization Branding multi-tenant ?
Supabase Auth ne prend pas en charge Per-Organization Branding multi-tenant. No per-organization or per-tenant branding in Supabase Auth. The auth UI theme is configured project-wide. Per-tenant branding must be fully custom-built. En savoir plus
Supabase Auth prend-il en charge Per-Organization MFA Policy multi-tenant ?
Supabase Auth ne prend pas en charge Per-Organization MFA Policy multi-tenant. MFA policy is configured globally per project, not per tenant or organization. Per-tenant MFA enforcement requires custom application logic. En savoir plus
Supabase Auth prend-il en charge Hosted / Universal Login Page fonctionnalité de branding ?
Supabase Auth prend partiellement en charge Hosted / Universal Login Page fonctionnalité de branding. No centrally hosted login page like Auth0 Universal Login. Auth UI must be embedded in the developer's application using the @supabase/auth-ui-react library or a custom implementation. A minimal hosted sign-in/sign-up UI is available in the Supabase dashboard for admin use only. En savoir plus
Supabase Auth prend-il en charge Embedded / Native Login Components fonctionnalité de branding ?
Supabase Auth prend en charge Embedded / Native Login Components fonctionnalité de branding. Auth is designed to be embedded in the application. The supabase-js SDK handles all auth flows client-side. The @supabase/auth-ui-react library provides pre-built React components for sign-in, sign-up, and password reset flows. En savoir plus
Supabase Auth prend-il en charge White-Label / Full Brand Removal fonctionnalité de branding ?
Supabase Auth prend en charge White-Label / Full Brand Removal fonctionnalité de branding. Full white-labeling available. Since Supabase Auth is open source (Apache 2.0), the entire auth layer can be customized. Email templates can remove Supabase branding on Pro+ plans. En savoir plus
Supabase Auth prend-il en charge Localization / i18n fonctionnalité de branding ?
Supabase Auth prend partiellement en charge Localization / i18n fonctionnalité de branding. The @supabase/auth-ui-react library has limited built-in i18n support. Localization must be handled at the application layer. Email templates support custom text but lack a translation framework. Auth error messages from the server are English-only. En savoir plus
Supabase Auth prend-il en charge Prebuilt UI Components (SDK) fonctionnalité de branding ?
Supabase Auth prend en charge Prebuilt UI Components (SDK) fonctionnalité de branding. @supabase/auth-ui-react provides prebuilt React components for common auth flows (sign-in, sign-up, magic link, forgot password, social login buttons). Themed with appearance props. Community UI kits available for Next.js, SvelteKit, and others. En savoir plus
Supabase Auth prend-il en charge Login / Auth Analytics Dashboard analytique ?
Supabase Auth prend partiellement en charge Login / Auth Analytics Dashboard analytique. Basic auth metrics (sign-in counts, error rates) available in the Supabase dashboard. No dedicated authentication analytics dashboard. Detailed analytics require exporting logs to BigQuery or an external tool via Log Drains. En savoir plus
Supabase Auth prend-il en charge SOC 2 Type II Certification conformité ?
Supabase Auth prend en charge SOC 2 Type II Certification conformité. SOC 2 Type 2 compliant. SOC 2 reports are available to Team and Enterprise customers via the Supabase dashboard. En savoir plus
Supabase Auth prend-il en charge ISO 27001 / 27017 / 27018 Certification conformité ?
Supabase Auth prend en charge ISO 27001 / 27017 / 27018 Certification conformité. ISO 27001 certified. Certificate available to Team and Enterprise customers. En savoir plus
Supabase Auth prend-il en charge HIPAA Business Associate Agreement (BAA) conformité ?
Supabase Auth prend partiellement en charge HIPAA Business Associate Agreement (BAA) conformité. HIPAA BAA available on Team and Enterprise plans for storing Protected Health Information. Requires signing a Business Associate Agreement with Supabase. Not available on Free or Pro plans. En savoir plus
Supabase Auth prend-il en charge PCI DSS Compliance conformité ?
Supabase Auth ne prend pas en charge PCI DSS Compliance conformité. Supabase is not PCI DSS certified. Payment processing on the Supabase platform is handled by Stripe (PCI Level 1), but Supabase itself does not claim PCI compliance for customer workloads. En savoir plus
Supabase Auth prend-il en charge CSA STAR Certification conformité ?
Supabase Auth ne prend pas en charge CSA STAR Certification conformité. CSA STAR certification not mentioned in Supabase security documentation. En savoir plus
Supabase Auth prend-il en charge FedRAMP Authorization conformité ?
Supabase Auth ne prend pas en charge FedRAMP Authorization conformité. FedRAMP authorization is not held by Supabase. Supabase is not suitable for US federal government workloads requiring FedRAMP. En savoir plus
Supabase Auth prend-il en charge GDPR: Data Export (Portability) conformité ?
Supabase Auth prend en charge GDPR: Data Export (Portability) conformité. User data export possible via SQL queries on auth.users and associated tables, and via the Admin API. GDPR data portability (Article 20) supported through direct database access. En savoir plus
Supabase Auth prend-il en charge GDPR: Right to be Forgotten (User Deletion) conformité ?
Supabase Auth prend en charge GDPR: Right to be Forgotten (User Deletion) conformité. User deletion via Admin API deleteUser() removes the auth record. Application data in other tables should use ON DELETE CASCADE foreign keys to auto-delete. Developers responsible for purging data from storage buckets and other services. En savoir plus
Supabase Auth prend-il en charge Consent Management conformité ?
Supabase Auth ne prend pas en charge Consent Management conformité. No built-in consent management or cookie consent flows. Must be implemented at the application layer. En savoir plus
Supabase Auth prend-il en charge Region Deployment conformité ?
Supabase Auth prend en charge Region Deployment conformité. 17 AWS regions available: US West (N. California, Oregon), US East (N. Virginia, Ohio), Canada Central, South America (São Paulo), EU West (Ireland, London, Paris), EU Central (Frankfurt, Zurich), EU North (Stockholm), Asia Pacific (Mumbai, Singapore, Tokyo, Seoul, Sydney). En savoir plus
Supabase Auth prend-il en charge Private Cloud Deployment conformité ?
Supabase Auth prend en charge Private Cloud Deployment conformité. Supabase Cloud runs on AWS. Self-hosted deployment is fully supported (Docker Compose or Kubernetes) on any cloud provider or on-premises. Enterprise plan includes Bring Your Own Cloud (BYO Cloud) for dedicated infrastructure managed by Supabase. En savoir plus
Supabase Auth prend-il en charge SDK Coverage intégration développeur ?
Supabase Auth prend en charge SDK Coverage intégration développeur. Official Supabase SDKs: supabase-js (JavaScript/TypeScript), supabase-dart (Flutter/Dart), supabase-swift (iOS), supabase-kt (Kotlin/Android), supabase-py (Python), supabase-csharp (.NET). Community SDKs for Go, Ruby, Rust. Auth UI React/SvelteKit. Next.js and SvelteKit SSR auth helpers. En savoir plus
Supabase Auth prend-il en charge Management API intégration développeur ?
Supabase Auth prend en charge Management API intégration développeur. Full Admin REST API for user management (CRUD), SSO configuration, and MFA management. Requires service role key (bypasses RLS). Available in all official SDKs under the auth.admin namespace. Management API also available for project-level configuration. En savoir plus
Supabase Auth prend-il en charge Authentication API Rate Limits intégration développeur ?
Supabase Auth prend en charge Authentication API Rate Limits intégration développeur. Documented per-endpoint rate limits: signup/magic link: 2/hour with built-in SMTP (unlimited with custom SMTP); OTP: 30/hour project-wide; token refresh: 1,800/hour per IP (burst: 30); verify: 360/hour per IP (burst: 30); MFA challenge/verify: 15/hour per IP; anonymous sign-ins: 30/hour per IP. Some limits configurable via dashboard. En savoir plus
Supabase Auth prend-il en charge Actions / Extensibility Pipeline intégration développeur ?
Supabase Auth prend en charge Actions / Extensibility Pipeline intégration développeur. Auth Hooks provide six extensibility points: Before User Created, Custom Access Token (add JWT claims), Send SMS (custom provider), Send Email (custom provider), MFA Verification Attempt (custom MFA logic), Password Verification Attempt (custom password checks / lazy migration). Hooks implemented as Postgres functions or HTTPS endpoints (Edge Functions or external). Signed payloads for security. En savoir plus
Supabase Auth prend-il en charge TypeScript Support in Extensibility intégration développeur ?
Supabase Auth prend en charge TypeScript Support in Extensibility intégration développeur. Auth Hooks implemented as Edge Functions run on Deno and support TypeScript natively. Postgres function hooks are written in PL/pgSQL or PL/v8 (JavaScript/TypeScript). En savoir plus
Supabase Auth prend-il en charge Custom Domain intégration développeur ?
Supabase Auth prend en charge Custom Domain intégration développeur. Custom domain available as a paid add-on ($10/month per domain per project) on paid plans. Only one custom domain per project. CNAME records only — not compatible with root domain A records. Activating/removing a custom domain requires re-configuring OAuth and SAML integrations. En savoir plus
Supabase Auth prend-il en charge Deploy CLI (Infrastructure as Code) intégration développeur ?
Supabase Auth prend en charge Deploy CLI (Infrastructure as Code) intégration développeur. Supabase CLI supports full project configuration as code: auth settings via config.toml, database migrations, Edge Functions deployment, and local development with supabase start. CI/CD integration via GitHub Actions. En savoir plus
Supabase Auth prend-il en charge Terraform Provider intégration développeur ?
Supabase Auth prend en charge Terraform Provider intégration développeur. Official Supabase Terraform provider for managing projects, auth configuration, edge functions, and database settings. Available in the Terraform Registry. En savoir plus
Supabase Auth prend-il en charge Custom Database Connections intégration développeur ?
Supabase Auth prend en charge Custom Database Connections intégration développeur. Supabase Auth stores user data in a Postgres auth schema — fully accessible via SQL. Developers have direct access to the underlying Postgres database for custom queries, triggers, and integrations. The auth schema is separate from the public schema but queryable with the service role. En savoir plus
Supabase Auth prend-il en charge Native Webhook Support intégration développeur ?
Supabase Auth prend en charge Native Webhook Support intégration développeur. Auth Hooks act as synchronous webhooks at auth flow points (HTTP endpoint or Postgres function). Database webhooks via pg_net extension for async event notifications. Edge Functions can be triggered on database changes for post-auth workflows. En savoir plus
Supabase Auth prend-il en charge Universal Login / Hosted Login Page Customization intégration développeur ?
Supabase Auth prend partiellement en charge Universal Login / Hosted Login Page Customization intégration développeur. No centrally hosted login page. Auth UI customization done via the @supabase/auth-ui-react library using appearance props, custom CSS variables, and theme overrides. Email template customization (13 template types) available in the Auth settings. Full custom UI builds are the recommended approach for production. En savoir plus
Supabase Auth prend-il en charge Custom Email Provider (SMTP) intégration développeur ?
Supabase Auth prend en charge Custom Email Provider (SMTP) intégration développeur. Custom SMTP provider configurable on all plans. Works with any SMTP-compatible service (Resend, AWS SES, Postmark, SendGrid, Brevo, ZeptoMail, etc.). Built-in SMTP is limited to 2 emails/hour with no SLA — custom SMTP is required for production. The Send Email Auth Hook enables routing via non-SMTP providers. En savoir plus
Supabase Auth prend-il en charge Email Templates intégration développeur ?
Supabase Auth prend en charge Email Templates intégration développeur. 13 customizable email templates: 6 authentication (confirm signup, invite user, magic link/OTP, change email, reset password, reauthentication) and 7 security notifications (password changed, email changed, phone changed, sign-in method linked/removed, verification method added/removed). Templates use Go Templates syntax with variables like {{ .ConfirmationURL }} and {{ .Token }}. Configured via dashboard or config.toml. En savoir plus
Supabase Auth prend-il en charge Custom OIDC Claims / Token Enrichment intégration développeur ?
Supabase Auth prend en charge Custom OIDC Claims / Token Enrichment intégration développeur. Custom JWT claims added via the Custom Access Token Auth Hook. The hook receives the standard claims and can add, modify, or remove claims before the token is signed. Available on all plans. Hooks implemented as Postgres functions or HTTP endpoints. En savoir plus
Supabase Auth prend-il en charge No-Code Auth Flow Builder / Orchestration fonctionnalité ?
Supabase Auth ne prend pas en charge No-Code Auth Flow Builder / Orchestration fonctionnalité. No visual/no-code authentication flow builder. Flows are configured programmatically via the supabase-js SDK and Auth Hooks. En savoir plus
Supabase Auth prend-il en charge Identity Verification / Document Proofing fonctionnalité ?
Supabase Auth ne prend pas en charge Identity Verification / Document Proofing fonctionnalité. No built-in identity document verification or biometric liveness proofing. Must integrate third-party services at the application layer. En savoir plus
Supabase Auth prend-il en charge Decentralized / Verifiable Credentials fonctionnalité ?
Supabase Auth ne prend pas en charge Decentralized / Verifiable Credentials fonctionnalité. No support for W3C Verifiable Credentials, Decentralized Identifiers (DIDs), or wallet-based authentication. En savoir plus
Supabase Auth prend-il en charge Built-in Billing / Subscription Management fonctionnalité ?
Supabase Auth ne prend pas en charge Built-in Billing / Subscription Management fonctionnalité. No native billing or subscription management integration. Billing must be handled via third-party services (Stripe, etc.) at the application layer. En savoir plus
Supabase Auth prend-il en charge Agentic AI / MCP Server Authentication fonctionnalité ?
Supabase Auth prend partiellement en charge Agentic AI / MCP Server Authentication fonctionnalité. OAuth 2.1 authorization server supports MCP (Model Context Protocol) authentication flows for AI agent identity. No dedicated MCP auth tooling yet — implementable using the existing OAuth 2.1 client credentials and token exchange flows. En savoir plus
Supabase Auth prend-il en charge Post-Quantum Hybrid TLS Key Exchange fonctionnalité de cryptographie post-quantique ?
Supabase Auth prend partiellement en charge Post-Quantum Hybrid TLS Key Exchange fonctionnalité de cryptographie post-quantique. Supabase's own security page states it uses 'protection at the CDN level via Cloudflare' in addition to fail2ban, confirming Cloudflare fronts at least part of Supabase's platform. Cloudflare has enabled hybrid post-quantum (X25519Kyber768/X25519MLKEM768) TLS 1.3 key exchange by default across its edge network since 2023-2024. This is infra-level, Cloudflare-driven support, not a GoTrue/Supabase Auth-specific implementation, and Supabase has made no direct statement about PQC. En savoir plus
Supabase Auth prend-il en charge Post-Quantum Digital Signature Algorithms fonctionnalité de cryptographie post-quantique ?
Supabase Auth ne prend pas en charge Post-Quantum Digital Signature Algorithms fonctionnalité de cryptographie post-quantique. No public evidence found that Supabase Auth (GoTrue) supports ML-DSA/SLH-DSA/Falcon for JWT signing. Supabase Auth uses standard JOSE algorithms (HS256/RS256/ES256/etc.); no PQC algorithm support is documented.
Supabase Auth prend-il en charge Post-Quantum Token & Data Encryption fonctionnalité de cryptographie post-quantique ?
Supabase Auth ne prend pas en charge Post-Quantum Token & Data Encryption fonctionnalité de cryptographie post-quantique. No public evidence found that the provider supports ML-KEM or HPKE (RFC 9180) for encrypting JWE tokens, SAML assertions, or user secrets.
Supabase Auth prend-il en charge Post-Quantum Certificate & mTLS Support fonctionnalité de cryptographie post-quantique ?
Supabase Auth ne prend pas en charge Post-Quantum Certificate & mTLS Support fonctionnalité de cryptographie post-quantique. No public evidence found of post-quantum or hybrid X.509 digital certificate support for mTLS client authentication or federation endpoints.
Supabase Auth prend-il en charge Post-Quantum Stateful Hash Signatures fonctionnalité de cryptographie post-quantique ?
Supabase Auth ne prend pas en charge Post-Quantum Stateful Hash Signatures fonctionnalité de cryptographie post-quantique. No public evidence found of NIST SP 800-208 stateful hash-based signature scheme support (LMS/HSS, XMSS).
Comparer avec d'autres fournisseurs
Remarque : Les données actuelles sont basées sur la documentation/l'expérience des fournisseurs et peuvent ne pas être exactes à 100 %. Veuillez ouvrir un ticket si vous avez constaté des incohérences.