Hi @joe.pringle
Welcome to the Auth0 Community!
You are asking whether Auth0 can formally confirm that its endpoints are OIDC/OAuth 2.0 protocol endpoints only, and that no path accepts or stores arbitrary data written by a customer or an end user.
[Summary]
Auth0’s core authentication endpoints process identity data only, but Auth0 does provide documented Management API and metadata features that let tenant administrators and applications write data, so a formal written statement from Auth0 is needed to cover the full “no write path” claim.
[Root Cause]
The primary customer-facing endpoints, /authorize, /token, /userinfo, and /v2/logout, implement OpenID Connect, OAuth 2.0, and SAML protocols. These endpoints process identity attributes (such as email address, name, and identity provider connection), JWTs and opaque refresh tokens, and hashed credentials. They are not designed to accept arbitrary application data. Other Auth0 APIs, however, are authenticated and documented, and they can write data in specific ways.
[Solution]
1. Protocol Endpoints (Transient Transactional Data)
The endpoints that end-users directly interact with—such as /authorize, /oauth/token, /userinfo, and /v2/logout—act as a transactional runtime engine. They do not serve as a general-purpose database for proprietary application data.
The data processed in these paths is strictly limited to:
-
Identity attributes: Basic user profile data (e.g., email address, name, sub identifier, and the connection provider) required to validate identity.
-
Token material: Issuing short-lived JSON Web Tokens (JWTs) and managing opaque, securely hashed refresh tokens.
-
Credentials: User passwords, which are strictly hashed utilizing bcrypt/Argon2 and salted before storage, or WebAuthn/FIDO2 public key credentials for passkeys.
2. The Management API Surface (Persistent Configuration Data)
It is crucial to note that Auth0’s Management API (/api/v2/) contains numerous endpoints that persistently write and store data on behalf of your tenant. These endpoints are designed for Machine-to-Machine (M2M) and administrative operations and manage:
-
User Accounts: Persistent user profile records.
-
Branding & Templates: Storing custom HTML page templates, email provider settings, and localization assets.
-
Extensions & Custom Logic: Storing Rules, Custom Database Scripts, Hooks, and Auth0 Actions code.
-
Audit Logs: Storing real-time tenant log history (e.g., successful logins, blocked attempts, and configuration changes).
Metadata Storage Recommendations
While Auth0 offers custom metadata storage within user profiles via app_metadata (which cannot be edited by the end-user) and user_metadata (user-editable), we strongly recommend against storing any proprietary, highly sensitive, or regulated customer data (such as financial records, PHI, or PII beyond basic identity) in these fields.
3. Compliance and Security Trust Center
For formal compliance evaluations and security audits (such as SOC 2 Type II, ISO 27001, or PCI-DSS Attestation of Compliance), we recommend utilizing Auth0’s dedicated trust and security channels:
Additional Reference Materials
I hope this clarifies the taxonomy of Auth0’s endpoints and provides your security team with the exact resources they need. Please let us know if we can assist you with any further security reviews!
Have a great one,
Gerald