SuperTokens Fournisseur IAM

Open-source embedded authentication with no redirects — auth runs on your own domain. Recipe-based modular architecture. Self-hostable for free on PostgreSQL or MySQL, with optional managed cloud. Core differentiator: no hosted login page, no vendor domain in the auth flow.

Fonctionnalités

Authentification multi-facteurs (MFA)

Time-based One-Time Password (TOTP)
HMAC-based One-Time Password (HOTP)
Universal 2nd Factor (U2F)
WebAuthn
Email Code
Phone Code
Recovery Code
Push Notification
Adaptive / Risk-Based MFA
Cisco Duo
Step-Up Authentication

Protocoles d'intégration

OpenID Connect (OIDC)
SAML 2.0
WS-Federation
Machine-to-Machine (M2M) Authentication

Fédération d'identité

OpenID Connect (OIDC) Federation
SAML 2.0 Federation
Active Directory / LDAP
Azure Active Directory (Entra ID)

Contrôle d'accès et autorisation

Attribute-Based Access Control (ABAC)
Fine-Grained Authorization (FGA / ReBAC)
API Authorization (Scopes / Permissions)

Sécurité

Audit Log Retention
Audit Log Streaming
Security Center (Threat Monitoring Dashboard)
Encryption at Rest
Encryption in Transit
Customer Managed Keys (BYOK)
Bot Detection
Brute Force Protection
Suspicious IP Throttling
Breached Password Detection
Credential Guard (Dark Web Monitoring)
Tenant Access Control List (IP ACL)
Device Fingerprinting

Multi-Tenancy / Organisations

Per-Organization Branding
Per-Organization MFA Policy

Branding et UX

Hosted / Universal Login Page
Embedded / Native Login Components
White-Label / Full Brand Removal
Localization / i18n
Prebuilt UI Components (SDK)

Analytique et audit

Login / Auth Analytics Dashboard

Conformité

SOC 2 Type II Certification
ISO 27001 / 27017 / 27018 Certification
HIPAA Business Associate Agreement (BAA)
PCI DSS Compliance
CSA STAR Certification
FedRAMP Authorization
GDPR: Data Export (Portability)
GDPR: Right to be Forgotten (User Deletion)
Consent Management
Region Deployment
🇺🇸US🇪🇺EU🇸🇪🇱🇫🇒🇭🇴🇸🇹🇪🇩Self-hosted
Private Cloud Deployment
AWSAzureGCPOn-premises

Intégration développeur

SDK Coverage
JavaScriptTypeScriptReactReact NativeNext.jsNode.jsPythonGoJava.NETSwiftKotlinFlutter
Management API
Authentication API Rate Limits
Actions / Extensibility Pipeline
TypeScript Support in Extensibility
Custom Domain
Deploy CLI (Infrastructure as Code)
Terraform Provider
Custom Database Connections
Native Webhook Support
Universal Login / Hosted Login Page Customization
Custom Email Provider (SMTP)
Email Templates
Custom OIDC Claims / Token Enrichment

Avancé / Différenciateurs

No-Code Auth Flow Builder / Orchestration
Identity Verification / Document Proofing
Decentralized / Verifiable Credentials
Built-in Billing / Subscription Management
Agentic AI / MCP Server Authentication

Cryptographie post-quantique

Post-Quantum Hybrid TLS Key Exchange
Post-Quantum Digital Signature Algorithms
Post-Quantum Migration Roadmap
Post-Quantum Token & Data Encryption
Post-Quantum Certificate & mTLS Support
Post-Quantum Stateful Hash Signatures

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

SuperTokens prend-il en charge Nom d'utilisateur et mot de passe méthode d'authentification ?

SuperTokens prend en charge Nom d'utilisateur et mot de passe méthode d'authentification. Email/password authentication via the EmailPassword recipe. Supports sign-up, sign-in, email verification, and password reset flows. Username-based auth also available via the EmailPassword recipe with username as the login identifier. Pre-built React and React Native UI components included. En savoir plus

SuperTokens prend-il en charge Connexion sociale méthode d'authentification ?

SuperTokens prend en charge Connexion sociale méthode d'authentification. Social login via the ThirdParty recipe. Built-in providers: Google, GitHub, Facebook, Apple, GitLab, Twitter/X, Discord, Bitbucket, LinkedIn, Okta, Active Directory, and any generic OIDC/OAuth2 provider. Can be combined with email/password via the ThirdPartyEmailPassword recipe. En savoir plus

SuperTokens prend-il en charge Passkey méthode d'authentification ?

SuperTokens prend en charge Passkey méthode d'authentification. Passkeys (FIDO2/WebAuthn) supported as a primary authentication method via the WebAuthn recipe. Users can register and authenticate with biometric authenticators (Touch ID, Face ID, Windows Hello) or hardware security keys. Auth runs on the developer's own domain. En savoir plus

SuperTokens prend-il en charge Email Passwordless méthode d'authentification ?

SuperTokens prend en charge Email Passwordless méthode d'authentification. Email OTP (one-time code) for passwordless sign-in via the Passwordless recipe. Configurable code expiry and length. Can be combined with magic links in the same flow. SMTP configuration required. En savoir plus

SuperTokens prend-il en charge Phone Passwordless méthode d'authentification ?

SuperTokens prend en charge Phone Passwordless méthode d'authentification. Phone/SMS OTP for passwordless sign-in via the Passwordless recipe. Requires a configured SMS provider (Twilio, AWS SNS, or custom). Can be used alongside email OTP or standalone. En savoir plus

SuperTokens prend-il en charge Magic Link méthode d'authentification ?

SuperTokens prend en charge Magic Link méthode d'authentification. Email magic link sign-in via the Passwordless recipe. One-time-use links sent to the user's email. Configurable expiry. Can be combined with OTP codes in the same flow (user sees both options). En savoir plus

SuperTokens prend-il en charge Anonymous / Guest méthode d'authentification ?

SuperTokens prend en charge Anonymous / Guest méthode d'authentification. Anonymous sessions supported via the Session recipe — a session cookie is issued without requiring login. Developers track anonymous activity server-side and can link the session to a real user account upon sign-up. No dedicated 'anonymous user' record is created until conversion. En savoir plus

SuperTokens prend-il en charge Time-based One-Time Password (TOTP) MFA ?

SuperTokens prend en charge Time-based One-Time Password (TOTP) MFA. TOTP (Time-based One-Time Password) MFA via the TOTP recipe, part of the MFA module. Self-hosted: included at no extra cost. Managed cloud: +$0.01/MAU add-on (minimum $100/month). Works with any TOTP authenticator app (Google Authenticator, Authy, etc.). En savoir plus

SuperTokens prend-il en charge HMAC-based One-Time Password (HOTP) MFA ?

SuperTokens ne prend pas en charge HMAC-based One-Time Password (HOTP) MFA. Counter-based HOTP is not supported. The MFA module supports TOTP (time-based), email OTP, and phone/SMS OTP as second factors. En savoir plus

SuperTokens prend-il en charge Universal 2nd Factor (U2F) MFA ?

SuperTokens ne prend pas en charge Universal 2nd Factor (U2F) MFA. U2F hardware security keys are not supported as a standalone MFA factor. WebAuthn/passkeys are available as a primary authentication method (not as a second factor). U2F is the predecessor spec to WebAuthn and not separately implemented. En savoir plus

SuperTokens prend-il en charge WebAuthn MFA ?

SuperTokens ne prend pas en charge WebAuthn MFA. WebAuthn/passkeys are implemented as a primary authentication method in the WebAuthn recipe, not as an MFA second factor. Step-up to a passkey challenge as a second factor is not natively supported in the MFA module. En savoir plus

SuperTokens prend-il en charge Email Code MFA ?

SuperTokens prend en charge Email Code MFA. Email OTP as a second factor via the MFA module (Passwordless recipe as an MFA step). Self-hosted: included. Managed cloud: +$0.01/MAU add-on for the MFA module. En savoir plus

SuperTokens prend-il en charge Phone Code MFA ?

SuperTokens prend en charge Phone Code MFA. Phone/SMS OTP as a second factor via the MFA module. Requires a configured SMS provider (Twilio, AWS SNS, custom). Self-hosted: free. Managed cloud: +$0.01/MAU add-on for the MFA module. En savoir plus

SuperTokens prend-il en charge Recovery Code MFA ?

SuperTokens ne prend pas en charge Recovery Code MFA. Recovery/backup codes are not natively supported as a built-in MFA fallback. Developers must implement a custom recovery flow. En savoir plus

SuperTokens prend-il en charge Push Notification MFA ?

SuperTokens ne prend pas en charge Push Notification MFA. Push notification MFA (e.g., Duo push, custom push) is not natively supported. Not in the MFA module. En savoir plus

SuperTokens prend-il en charge Adaptive / Risk-Based MFA MFA ?

SuperTokens ne prend pas en charge Adaptive / Risk-Based MFA MFA. Risk-based or adaptive MFA is not natively supported. Custom adaptive logic can be implemented by overriding the MFA recipe functions in the backend SDK to evaluate risk signals before requiring a second factor. En savoir plus

SuperTokens prend-il en charge Cisco Duo MFA ?

SuperTokens ne prend pas en charge Cisco Duo MFA. No native Cisco Duo integration. Duo can be reached indirectly via SAML/OIDC SSO federation (Enterprise plan only). En savoir plus

SuperTokens prend-il en charge Step-Up Authentication MFA ?

SuperTokens prend partiellement en charge Step-Up Authentication MFA. Step-up authentication can be implemented by inspecting the session's completed_factors claim and requiring additional MFA factors for sensitive operations. No built-in declarative step-up policy — requires custom logic in the backend SDK overrides. En savoir plus

SuperTokens prend-il en charge OpenID Connect (OIDC) protocole d'intégration ?

SuperTokens prend en charge OpenID Connect (OIDC) protocole d'intégration. SuperTokens acts as an OIDC/OAuth 2.1 provider. Issues JWTs with customizable claims for downstream service authorization. Standard OIDC endpoints available. Custom OIDC/OAuth2 providers can be added as social login via the ThirdParty recipe. En savoir plus

SuperTokens prend-il en charge SAML 2.0 protocole d'intégration ?

SuperTokens prend en charge SAML 2.0 protocole d'intégration. SAML 2.0 support available via the dedicated SAML recipe. Can act as a SAML SP connecting to external IdPs. Enterprise plan required for the SSO/SAML functionality in the managed cloud. En savoir plus

SuperTokens prend-il en charge WS-Federation protocole d'intégration ?

SuperTokens ne prend pas en charge WS-Federation protocole d'intégration. WS-Federation is not supported. SuperTokens supports OIDC and SAML 2.0 as federation protocols. En savoir plus

SuperTokens prend-il en charge Machine-to-Machine (M2M) Authentication protocole d'intégration ?

SuperTokens prend en charge Machine-to-Machine (M2M) Authentication protocole d'intégration. Machine-to-machine authentication via the M2M recipe. Enterprise plan required on managed cloud. Self-hosted deployments can use the M2M recipe without restriction. Implements OAuth 2.1 client credentials flow. En savoir plus

SuperTokens prend-il en charge OpenID Connect (OIDC) Federation fédération d'identité ?

SuperTokens prend en charge OpenID Connect (OIDC) Federation fédération d'identité. OIDC enterprise SSO federation via the ThirdParty recipe and dedicated SSO module. Enterprise plan required on managed cloud. Any OIDC-compliant IdP supported (Okta, Auth0, Google Workspace, etc.). Self-hosted includes this without restrictions. En savoir plus

SuperTokens prend-il en charge SAML 2.0 Federation fédération d'identité ?

SuperTokens prend en charge SAML 2.0 Federation fédération d'identité. SAML 2.0 enterprise IdP federation. Enterprise plan required on managed cloud. Any SAML 2.0 IdP supported (Microsoft Entra ID, Okta, etc.). Self-hosted deployments have full access to the SAML recipe. En savoir plus

SuperTokens prend-il en charge Active Directory / LDAP fédération d'identité ?

SuperTokens ne prend pas en charge Active Directory / LDAP fédération d'identité. No native LDAP or Active Directory connector. AD can be federated via SAML 2.0 or OIDC using Microsoft Entra ID (Azure AD) as an IdP via the ThirdParty recipe. En savoir plus

SuperTokens prend-il en charge Azure Active Directory (Entra ID) fédération d'identité ?

SuperTokens prend en charge Azure Active Directory (Entra ID) fédération d'identité. Microsoft Entra ID (Azure AD) supported as a social login provider via the ThirdParty recipe (OAuth2/OIDC). For enterprise SSO with SAML or OIDC federation, the Enterprise plan (or self-hosted) is required. En savoir plus

SuperTokens prend-il en charge Bulk User Import gestion des utilisateurs ?

SuperTokens prend en charge Bulk User Import gestion des utilisateurs. Bulk user import via the User Import API — accepts arrays of users with credentials, metadata, and roles. Supports importing users without triggering sign-up hooks. Available on all plans. En savoir plus

SuperTokens prend-il en charge Password Hash Import (Multiple Formats) gestion des utilisateurs ?

SuperTokens prend en charge Password Hash Import (Multiple Formats) gestion des utilisateurs. Password hash import supported for bcrypt, Argon2, and Firebase scrypt hashes. Users can sign in with their original passwords immediately post-migration without a reset step. En savoir plus

SuperTokens prend-il en charge Bulk User Export gestion des utilisateurs ?

SuperTokens ne prend pas en charge Bulk User Export gestion des utilisateurs. No dedicated REST API for bulk user export. On self-hosted deployments, users can be exported by querying the SuperTokens database (PostgreSQL or MySQL) directly. No export tooling provided out of the box. En savoir plus

SuperTokens prend-il en charge Bulk User Update / Delete gestion des utilisateurs ?

SuperTokens prend en charge Bulk User Update / Delete gestion des utilisateurs. Bulk user operations available via the Admin API (Node.js, Python, Go, Java, .NET). Delete, update metadata, and revoke sessions for multiple users programmatically. No single batch endpoint — requires scripted individual API calls. En savoir plus

SuperTokens prend-il en charge Upsert on Import gestion des utilisateurs ?

SuperTokens ne prend pas en charge Upsert on Import gestion des utilisateurs. The import API does not support upsert semantics. Importing a user whose email already exists will result in a duplicate or error. Pre-check for existing users before importing. En savoir plus

SuperTokens prend-il en charge Legacy Username Import (Non-Allowed Characters) gestion des utilisateurs ?

SuperTokens ne prend pas en charge Legacy Username Import (Non-Allowed Characters) gestion des utilisateurs. No special handling for importing legacy usernames with non-standard characters. The EmailPassword recipe uses email as the primary login identifier. Username-based auth requires using the username field which enforces alphanumeric constraints. En savoir plus

SuperTokens prend-il en charge MFA Enrollment Import gestion des utilisateurs ?

SuperTokens ne prend pas en charge MFA Enrollment Import gestion des utilisateurs. Importing pre-existing TOTP secrets or MFA enrollments is not supported. Users must re-enroll in MFA after migration. En savoir plus

SuperTokens prend-il en charge Inbound SCIM Provisioning gestion des utilisateurs ?

SuperTokens ne prend pas en charge Inbound SCIM Provisioning gestion des utilisateurs. SCIM 2.0 is not supported. User provisioning from enterprise IdPs must use the SuperTokens Admin API directly or a custom integration layer. En savoir plus

SuperTokens prend-il en charge Outbound SCIM Provisioning gestion des utilisateurs ?

SuperTokens ne prend pas en charge Outbound SCIM Provisioning gestion des utilisateurs. No outbound SCIM provisioning to downstream applications. En savoir plus

SuperTokens prend-il en charge SCIM Groups Provisioning gestion des utilisateurs ?

SuperTokens ne prend pas en charge SCIM Groups Provisioning gestion des utilisateurs. No SCIM group management. Groups and roles are managed via the User Roles recipe. En savoir plus

SuperTokens prend-il en charge Just-In-Time (JIT) User Provisioning gestion des utilisateurs ?

SuperTokens prend en charge Just-In-Time (JIT) User Provisioning gestion des utilisateurs. Just-in-time provisioning: users are automatically created on first social/ThirdParty login. The sign-up override hook allows custom logic during provisioning (e.g., role assignment, metadata enrichment). En savoir plus

SuperTokens prend-il en charge Lazy / Trickle Migration from Legacy Database gestion des utilisateurs ?

SuperTokens prend en charge Lazy / Trickle Migration from Legacy Database gestion des utilisateurs. Zero-downtime lazy migration supported: the EmailPassword sign-in override intercepts failed local auth, falls back to the legacy system to verify credentials, then creates the user locally on success. Bulk import API provides an alternative for pre-migration. Works on all plan tiers (self-hosted and managed cloud). En savoir plus

SuperTokens prend-il en charge Self-Service Profile Management Portal gestion des utilisateurs ?

SuperTokens prend partiellement en charge Self-Service Profile Management Portal gestion des utilisateurs. No built-in self-service profile management page. Users can update their own metadata and password via the SDK. Developers must build profile management UI using the supertokens-auth-react components or a custom implementation. En savoir plus

SuperTokens prend-il en charge User Account Linking gestion des utilisateurs ?

SuperTokens prend en charge User Account Linking gestion des utilisateurs. Account linking supported via the Account Linking recipe — merges multiple login methods (email/password, social, passwordless) into a single user record. Managed cloud: +$0.005/MAU add-on. Self-hosted: included at no extra cost. En savoir plus

SuperTokens prend-il en charge User Blocking / Banning gestion des utilisateurs ?

SuperTokens prend en charge User Blocking / Banning gestion des utilisateurs. Users can be banned/disabled via the Admin API or the built-in user management dashboard. Banned users have their active sessions revoked and cannot create new sessions. En savoir plus

SuperTokens prend-il en charge User Metadata gestion des utilisateurs ?

SuperTokens prend en charge User Metadata gestion des utilisateurs. Arbitrary user metadata stored via the User Metadata recipe (a dedicated key-value store per user). Accessible from both the backend SDK and the frontend SDK (with appropriate permissions). Available on all plans. En savoir plus

SuperTokens prend-il en charge Application Metadata gestion des utilisateurs ?

SuperTokens prend en charge Application Metadata gestion des utilisateurs. Admin-controlled metadata stored via the User Metadata recipe. Server-side update ensures that sensitive app metadata (e.g., roles, plan info) cannot be modified by the end user. Custom JWT claims include this metadata. En savoir plus

SuperTokens prend-il en charge Metadata Size Limits gestion des utilisateurs ?

SuperTokens prend partiellement en charge Metadata Size Limits gestion des utilisateurs. No officially documented metadata size limit. On self-hosted deployments, metadata is stored in the SuperTokens database (PostgreSQL or MySQL) as a JSON blob. Practical limits depend on database configuration. Large metadata payloads included in JWTs should be kept under 8 KB to avoid HTTP header issues. En savoir plus

SuperTokens prend-il en charge User Search gestion des utilisateurs ?

SuperTokens prend en charge User Search gestion des utilisateurs. User search available via the built-in Admin Dashboard (filter by email, phone, recipe type) and via the Admin API. Search by email, phone number, and thirdparty provider supported. Available on all plans. En savoir plus

SuperTokens prend-il en charge Role-Based Access Control (RBAC) gestion des utilisateurs ?

SuperTokens prend en charge Role-Based Access Control (RBAC) gestion des utilisateurs. Role-Based Access Control via the User Roles recipe. Create roles, assign permissions to roles, assign roles to users and tenants. Roles and permissions included in session JWTs. Built-in API for role/permission management. Dashboard for admin management. Available on all plans. En savoir plus

SuperTokens prend-il en charge Organizations (Multi-Tenancy B2B) gestion des utilisateurs ?

SuperTokens prend en charge Organizations (Multi-Tenancy B2B) gestion des utilisateurs. Multi-tenancy via the Multi-tenancy recipe. Each tenant has isolated user pools, login methods, and SSO configurations. Supports tenant creation/deletion via Admin API, per-tenant login page, and shared users across tenants. Available on all plans. En savoir plus

SuperTokens prend-il en charge Password Strength Policies gestion des utilisateurs ?

SuperTokens prend en charge Password Strength Policies gestion des utilisateurs. Password strength policy configurable in the EmailPassword recipe initialization: minimum length, require uppercase/lowercase/numbers/special characters. Custom validators can be added via the override mechanism for more complex policies. En savoir plus

SuperTokens prend-il en charge Username Restrictions gestion des utilisateurs ?

SuperTokens prend en charge Username Restrictions gestion des utilisateurs. Username format restrictions configurable in the EmailPassword recipe. Custom username validators can be added via the override mechanism. Uniqueness is enforced natively. En savoir plus

SuperTokens prend-il en charge Progressive Profiling / Forms gestion des utilisateurs ?

SuperTokens ne prend pas en charge Progressive Profiling / Forms gestion des utilisateurs. No built-in progressive profiling flow. Can be implemented at the application layer using User Metadata and custom UI. En savoir plus

SuperTokens prend-il en charge Attribute-Based Access Control (ABAC) contrôle d'accès ?

SuperTokens ne prend pas en charge Attribute-Based Access Control (ABAC) contrôle d'accès. No native attribute-based access control policy engine. Custom ABAC can be implemented by including user attributes in JWT claims and enforcing policies in application middleware. En savoir plus

SuperTokens prend-il en charge Fine-Grained Authorization (FGA / ReBAC) contrôle d'accès ?

SuperTokens ne prend pas en charge Fine-Grained Authorization (FGA / ReBAC) contrôle d'accès. No relationship-based or fine-grained authorization engine (no ReBAC, no OpenFGA integration). Authorization beyond RBAC must be implemented at the application layer. En savoir plus

SuperTokens prend-il en charge API Authorization (Scopes / Permissions) contrôle d'accès ?

SuperTokens prend en charge API Authorization (Scopes / Permissions) contrôle d'accès. Session JWT validation for API authorization. Backend SDKs provide middleware for all major frameworks (Express, FastAPI, Django, Spring, etc.) to verify sessions and check roles/permissions on each request. En savoir plus

SuperTokens prend-il en charge Audit Log Retention fonctionnalité de sécurité ?

SuperTokens prend partiellement en charge Audit Log Retention fonctionnalité de sécurité. On self-hosted deployments, auth events are written to the SuperTokens database tables — retention is controlled by the operator. Managed cloud has limited built-in log visibility. No dedicated audit log retention policy or configurable retention period on managed cloud. En savoir plus

SuperTokens prend-il en charge Audit Log Streaming fonctionnalité de sécurité ?

SuperTokens ne prend pas en charge Audit Log Streaming fonctionnalité de sécurité. No native audit log streaming to external SIEM or logging platforms. On self-hosted, logs can be captured from the database or application server and forwarded to external systems at the infrastructure level. En savoir plus

SuperTokens prend-il en charge Security Center (Threat Monitoring Dashboard) fonctionnalité de sécurité ?

SuperTokens ne prend pas en charge Security Center (Threat Monitoring Dashboard) fonctionnalité de sécurité. No dedicated security monitoring dashboard or threat intelligence center. Auth events visible in the built-in user management dashboard but no real-time security alerting. En savoir plus

SuperTokens prend-il en charge Encryption at Rest fonctionnalité de sécurité ?

SuperTokens prend en charge Encryption at Rest fonctionnalité de sécurité. Managed cloud: data encrypted at rest by the underlying cloud provider. Self-hosted: encryption at rest is the responsibility of the operator's infrastructure (e.g., encrypted EBS volumes, RDS encryption). En savoir plus

SuperTokens prend-il en charge Encryption in Transit fonctionnalité de sécurité ?

SuperTokens prend en charge Encryption in Transit fonctionnalité de sécurité. All SuperTokens Core API connections use TLS. Backend SDK to Core communication can be configured with API keys over HTTPS. Self-hosted: TLS must be configured by the operator at the reverse proxy or application level. En savoir plus

SuperTokens prend-il en charge Customer Managed Keys (BYOK) fonctionnalité de sécurité ?

SuperTokens ne prend pas en charge Customer Managed Keys (BYOK) fonctionnalité de sécurité. Customer-managed encryption keys not available on the managed cloud. Self-hosted deployments give full control over encryption keys at the database and storage level. En savoir plus

SuperTokens prend-il en charge Bot Detection fonctionnalité de sécurité ?

SuperTokens prend partiellement en charge Bot Detection fonctionnalité de sécurité. Bot detection available as part of the Attack Protection Suite (Enterprise plan). Includes CAPTCHA integration (reCAPTCHA v2/v3, Cloudflare Turnstile). Not included in Self-hosted or Managed Cloud standard plans. En savoir plus

SuperTokens prend-il en charge Brute Force Protection fonctionnalité de sécurité ?

SuperTokens prend en charge Brute Force Protection fonctionnalité de sécurité. Built-in rate limiting on sign-in attempts via the EmailPassword recipe. Failed attempts are tracked and throttled. Configurable via the recipe initialization. Available on all plans. En savoir plus

SuperTokens prend-il en charge Suspicious IP Throttling fonctionnalité de sécurité ?

SuperTokens prend partiellement en charge Suspicious IP Throttling fonctionnalité de sécurité. IP-level suspicious activity detection part of the Attack Protection Suite (Enterprise plan). Standard plans include only basic rate limiting without IP intelligence. En savoir plus

SuperTokens prend-il en charge Breached Password Detection fonctionnalité de sécurité ?

SuperTokens prend partiellement en charge Breached Password Detection fonctionnalité de sécurité. Breached/compromised password detection part of the Attack Protection Suite (Enterprise plan). Checks against known credential breach databases. Not available on Self-hosted or standard Managed Cloud plans without Enterprise. En savoir plus

SuperTokens prend-il en charge Credential Guard (Dark Web Monitoring) fonctionnalité de sécurité ?

SuperTokens ne prend pas en charge Credential Guard (Dark Web Monitoring) fonctionnalité de sécurité. No proactive dark web monitoring or credential stuffing guard. Breached password detection at sign-up/change is available on Enterprise plan only. En savoir plus

SuperTokens prend-il en charge Tenant Access Control List (IP ACL) fonctionnalité de sécurité ?

SuperTokens ne prend pas en charge Tenant Access Control List (IP ACL) fonctionnalité de sécurité. No tenant-level access control lists for restricting auth traffic by IP or geography. Access control must be enforced at the reverse proxy or application layer. En savoir plus

SuperTokens prend-il en charge Device Fingerprinting fonctionnalité de sécurité ?

SuperTokens ne prend pas en charge Device Fingerprinting fonctionnalité de sécurité. No built-in device fingerprinting. Sessions are cookie/JWT based without device-level identification. Third-party fingerprinting libraries can be integrated at the application layer. En savoir plus

SuperTokens prend-il en charge Per-Organization Branding multi-tenant ?

SuperTokens ne prend pas en charge Per-Organization Branding multi-tenant. No per-tenant branding support. The pre-built React UI uses global theme configuration. Per-tenant custom UI requires building a fully custom authentication flow. En savoir plus

SuperTokens prend-il en charge Per-Organization MFA Policy multi-tenant ?

SuperTokens ne prend pas en charge Per-Organization MFA Policy multi-tenant. MFA policies are configured globally, not per tenant. Per-tenant MFA enforcement requires custom logic in the MFA recipe override. En savoir plus

SuperTokens prend-il en charge Hosted / Universal Login Page fonctionnalité de branding ?

SuperTokens ne prend pas en charge Hosted / Universal Login Page fonctionnalité de branding. SuperTokens is embedded-only by design — a core architectural differentiator. There is no hosted login page or redirect-based auth flow. Auth UI runs entirely on the developer's own domain, eliminating the vendor's subdomain from the user journey. En savoir plus

SuperTokens prend-il en charge Embedded / Native Login Components fonctionnalité de branding ?

SuperTokens prend en charge Embedded / Native Login Components fonctionnalité de branding. Core product feature: auth runs on the developer's own domain with no redirects. Pre-built React and React Native UI components provided. The backend SDK exposes API routes that the frontend components communicate with directly. No cross-domain auth flow. En savoir plus

SuperTokens prend-il en charge White-Label / Full Brand Removal fonctionnalité de branding ?

SuperTokens prend en charge White-Label / Full Brand Removal fonctionnalité de branding. Full white-labeling by design — auth runs on the developer's own domain with no SuperTokens branding. The open-source UI components are fully customizable. CSS and component overrides supported. No paid brand-removal add-on required. En savoir plus

SuperTokens prend-il en charge Localization / i18n fonctionnalité de branding ?

SuperTokens prend partiellement en charge Localization / i18n fonctionnalité de branding. Pre-built UI components have limited built-in i18n support. Translation strings can be overridden in the component configuration for supported languages. Full localization for all languages requires building a custom UI. En savoir plus

SuperTokens prend-il en charge Prebuilt UI Components (SDK) fonctionnalité de branding ?

SuperTokens prend en charge Prebuilt UI Components (SDK) fonctionnalité de branding. Pre-built UI provided as supertokens-auth-react (React) and supertokens-react-native (React Native). Components for sign-in, sign-up, password reset, email verification, MFA enrollment, and session management. Customizable via theme overrides and override components. En savoir plus

SuperTokens prend-il en charge Login / Auth Analytics Dashboard analytique ?

SuperTokens prend partiellement en charge Login / Auth Analytics Dashboard analytique. Built-in admin dashboard shows user counts, active sessions, and basic user activity. No dedicated authentication analytics (funnel rates, MAU trends, geographic distribution). Detailed analytics require exporting data from the database on self-hosted, or integrating an external analytics platform. En savoir plus

SuperTokens prend-il en charge SOC 2 Type II Certification conformité ?

SuperTokens prend en charge SOC 2 Type II Certification conformité. SuperTokens is SOC 2 Type 2 certified. The certification covers the managed cloud service. En savoir plus

SuperTokens prend-il en charge ISO 27001 / 27017 / 27018 Certification conformité ?

SuperTokens ne prend pas en charge ISO 27001 / 27017 / 27018 Certification conformité. ISO 27001 certification is not held by SuperTokens. Self-hosted deployments rely on the developer's own infrastructure compliance. En savoir plus

SuperTokens prend-il en charge HIPAA Business Associate Agreement (BAA) conformité ?

SuperTokens ne prend pas en charge HIPAA Business Associate Agreement (BAA) conformité. HIPAA BAA is not available. For HIPAA-regulated workloads, self-hosted deployment on HIPAA-compliant infrastructure is the recommended path. En savoir plus

SuperTokens prend-il en charge PCI DSS Compliance conformité ?

SuperTokens ne prend pas en charge PCI DSS Compliance conformité. PCI DSS compliance is not certified. SuperTokens is an authentication service and does not process payment data. En savoir plus

SuperTokens prend-il en charge CSA STAR Certification conformité ?

SuperTokens ne prend pas en charge CSA STAR Certification conformité. CSA STAR certification not held by SuperTokens. En savoir plus

SuperTokens prend-il en charge FedRAMP Authorization conformité ?

SuperTokens ne prend pas en charge FedRAMP Authorization conformité. FedRAMP authorization not held by SuperTokens. Self-hosted deployment on FedRAMP-authorized cloud infrastructure is required for federal government use cases. En savoir plus

SuperTokens prend-il en charge GDPR: Data Export (Portability) conformité ?

SuperTokens prend en charge GDPR: Data Export (Portability) conformité. User data export via the Admin API (get user by ID, list sessions, get metadata). On self-hosted deployments, direct database access enables bulk export. Developers are responsible for exporting data from all related application tables. En savoir plus

SuperTokens prend-il en charge GDPR: Right to be Forgotten (User Deletion) conformité ?

SuperTokens prend en charge GDPR: Right to be Forgotten (User Deletion) conformité. User deletion via the Admin API deletes the SuperTokens user record, sessions, metadata, roles, and third-party identities. Application data in external databases must be deleted separately. En savoir plus

SuperTokens prend-il en charge Consent Management conformité ?

SuperTokens ne prend pas en charge Consent Management conformité. No built-in consent management module. Consent must be captured and stored at the application layer using User Metadata. En savoir plus

SuperTokens prend-il en charge Region Deployment conformité ?

SuperTokens prend en charge Region Deployment conformité. Self-hosted deployments give full data residency control — deploy anywhere. Managed cloud region selection available (US and EU). For strict data residency requirements, self-hosting is recommended. En savoir plus

SuperTokens prend-il en charge Private Cloud Deployment conformité ?

SuperTokens prend en charge Private Cloud Deployment conformité. Open-source core is self-hostable on any cloud provider or on-premises with PostgreSQL or MySQL as the backend database. Docker images and Helm charts available. Enterprise plan provides SLA-backed managed deployments with multiple availability zones. En savoir plus

SuperTokens prend-il en charge SDK Coverage intégration développeur ?

SuperTokens prend en charge SDK Coverage intégration développeur. Backend SDKs: Node.js (Express, Hapi, Fastify, Koa, Nest.js), Python (Django, FastAPI, Flask), Go (net/http, Chi, Gin, Fiber), Java (Spring Boot), .NET (ASP.NET Core). Frontend SDKs: React, React Native, Vanilla JS, Next.js (app + pages router). Mobile: iOS (Swift), Android (Kotlin), Flutter. 25+ frameworks supported. En savoir plus

SuperTokens prend-il en charge Management API intégration développeur ?

SuperTokens prend en charge Management API intégration développeur. SuperTokens Core exposes a REST API (accessible only from the backend SDK or with an API key). Full user management: CRUD operations, session management, roles/permissions, metadata, MFA enrollment, tenant management. Swagger-documented. En savoir plus

SuperTokens prend-il en charge Authentication API Rate Limits intégration développeur ?

SuperTokens prend en charge Authentication API Rate Limits intégration développeur. Rate limits on sign-in attempts configurable in the EmailPassword recipe. Core API has built-in rate limiting on failed auth attempts. Self-hosted: additional infrastructure-level rate limiting (Nginx, load balancer) controlled by the operator. En savoir plus

SuperTokens prend-il en charge Actions / Extensibility Pipeline intégration développeur ?

SuperTokens prend en charge Actions / Extensibility Pipeline intégration développeur. Override any recipe function in the backend SDK: sign-up, sign-in, token creation, session refresh, sign-out, etc. Full control over all auth lifecycle events without limits on execution environment. Overrides are written in the same language as the backend SDK (Node.js, Python, Go, Java, .NET). En savoir plus

SuperTokens prend-il en charge TypeScript Support in Extensibility intégration développeur ?

SuperTokens prend en charge TypeScript Support in Extensibility intégration développeur. Node.js backend SDK is written in TypeScript with full TypeScript support for all recipe overrides. Python, Go, Java, and .NET SDKs support their respective type systems. En savoir plus

SuperTokens prend-il en charge Custom Domain intégration développeur ?

SuperTokens prend en charge Custom Domain intégration développeur. Auth runs on the developer's own domain by default — no configuration required. The SuperTokens Core API is deployed at a developer-specified URL (typically an internal service URL). The frontend SDK is configured to point to the developer's own backend routes. En savoir plus

SuperTokens prend-il en charge Deploy CLI (Infrastructure as Code) intégration développeur ?

SuperTokens ne prend pas en charge Deploy CLI (Infrastructure as Code) intégration développeur. No official CLI tool for SuperTokens deployment or configuration management. Infrastructure is managed via Docker, Helm charts, or cloud provider tooling. Configuration is done via environment variables and the backend SDK initialization. En savoir plus

SuperTokens prend-il en charge Terraform Provider intégration développeur ?

SuperTokens ne prend pas en charge Terraform Provider intégration développeur. No official Terraform provider for SuperTokens. Infrastructure provisioning is managed via standard cloud infrastructure tools. Community contributions exist but are not officially maintained. En savoir plus

SuperTokens prend-il en charge Custom Database Connections intégration développeur ?

SuperTokens prend en charge Custom Database Connections intégration développeur. SuperTokens Core requires PostgreSQL or MySQL as the backend database. Self-hosted deployments use the operator's existing database infrastructure. No custom connector scripts needed — SuperTokens manages its own schema within the configured database. En savoir plus

SuperTokens prend-il en charge Native Webhook Support intégration développeur ?

SuperTokens prend en charge Native Webhook Support intégration développeur. Webhooks supported via the recipe override mechanism and outgoing HTTP calls from backend SDK overrides. Any auth lifecycle event can trigger an outbound webhook. No hosted webhook management UI — implemented in backend code. En savoir plus

SuperTokens prend-il en charge Universal Login / Hosted Login Page Customization intégration développeur ?

SuperTokens ne prend pas en charge Universal Login / Hosted Login Page Customization intégration développeur. No hosted login page to customize. SuperTokens is embedded-only — the developer owns the entire UI. Customization is done via component override props and CSS in the supertokens-auth-react library. En savoir plus

SuperTokens prend-il en charge Custom Email Provider (SMTP) intégration développeur ?

SuperTokens prend en charge Custom Email Provider (SMTP) intégration développeur. Custom email provider configurable in recipe initialization via the emailDelivery.override field. Send email via any SMTP server or HTTP API (SendGrid, SES, Mailgun, Postmark, etc.) by overriding the sendEmail function in the backend SDK. En savoir plus

SuperTokens prend-il en charge Email Templates intégration développeur ?

SuperTokens prend en charge Email Templates intégration développeur. Built-in email templates for email verification, password reset, magic link, and OTP flows. Fully customizable — override the sendEmail function to modify subject, body, and sender. HTML and plaintext templates supported. En savoir plus

SuperTokens prend-il en charge Custom OIDC Claims / Token Enrichment intégration développeur ?

SuperTokens prend en charge Custom OIDC Claims / Token Enrichment intégration développeur. Custom JWT/session claims added via the Session recipe override (createNewSession or getAccessTokenPayload). Any additional data can be included in the access token payload. Session claim validators enforce claim presence/value on the frontend. En savoir plus

SuperTokens prend-il en charge No-Code Auth Flow Builder / Orchestration fonctionnalité ?

SuperTokens ne prend pas en charge No-Code Auth Flow Builder / Orchestration fonctionnalité. No visual/no-code authentication flow builder. Auth flows are configured programmatically in the backend SDK recipe initialization. En savoir plus

SuperTokens prend-il en charge Identity Verification / Document Proofing fonctionnalité ?

SuperTokens ne prend pas en charge Identity Verification / Document Proofing fonctionnalité. No built-in identity document verification or biometric liveness proofing. Must be integrated at the application layer via third-party services. En savoir plus

SuperTokens prend-il en charge Decentralized / Verifiable Credentials fonctionnalité ?

SuperTokens ne prend pas en charge Decentralized / Verifiable Credentials fonctionnalité. No support for W3C Verifiable Credentials, DIDs, or wallet-based authentication. En savoir plus

SuperTokens prend-il en charge Built-in Billing / Subscription Management fonctionnalité ?

SuperTokens ne prend pas en charge Built-in Billing / Subscription Management fonctionnalité. No native billing or subscription management integration. Must be handled at the application layer via third-party billing services. En savoir plus

SuperTokens prend-il en charge Agentic AI / MCP Server Authentication fonctionnalité ?

SuperTokens ne prend pas en charge Agentic AI / MCP Server Authentication fonctionnalité. No native MCP (Model Context Protocol) authorization or AI agent identity flows. OAuth 2.1 M2M tokens (Enterprise plan) can be used for machine-to-machine agent authentication but without dedicated MCP-spec tooling. En savoir plus

SuperTokens prend-il en charge Post-Quantum Digital Signature Algorithms fonctionnalité de cryptographie post-quantique ?

SuperTokens ne prend pas en charge Post-Quantum Digital Signature Algorithms fonctionnalité de cryptographie post-quantique. No public evidence found of ML-DSA/SLH-DSA/Falcon support for session JWT signing in SuperTokens. No GitHub issues or blog posts on PQC signature algorithms were found in the supertokens-core or related repositories.

SuperTokens prend-il en charge Post-Quantum Token & Data Encryption fonctionnalité de cryptographie post-quantique ?

SuperTokens 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.

SuperTokens prend-il en charge Post-Quantum Certificate & mTLS Support fonctionnalité de cryptographie post-quantique ?

SuperTokens 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.

SuperTokens prend-il en charge Post-Quantum Stateful Hash Signatures fonctionnalité de cryptographie post-quantique ?

SuperTokens 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).

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.