Auth0 identity provider emulation with OAuth 2.0 / OIDC, Universal Login pages, refresh token rotation, Userinfo, and Management API resources for users, roles, applications, organizations, and connections.
GET /.well-known/openid-configuration— OIDC discoveryGET /.well-known/jwks.json— JSON Web Key SetGET /authorize— authorization endpointGET /u/login— Universal Login pagePOST /oauth/token— token endpointGET /userinfo— user infoGET /v2/logout— logout
Authorization Code with PKCE is supported with both plain and S256 code challenge methods. The token endpoint supports authorization_code, refresh_token, and client_credentials.
Auth0 advertises tenant-aware URLs. With this config:
auth0:
tenant: my-tenantDiscovery returns endpoints under:
http://my-tenant.auth0.localhost:4012
For test environments that cannot route subdomains, call discovery with a tenant query parameter:
curl "http://localhost:4012/.well-known/openid-configuration?tenant=my-tenant"The returned endpoints include the same tenant parameter.
GET /api/v2/users— list usersPOST /api/v2/users— create userGET /api/v2/users/:id— get userPATCH /api/v2/users/:id— update userDELETE /api/v2/users/:id— delete userGET /api/v2/users/:id/roles— list user rolesPOST /api/v2/users/:id/roles— assign rolesGET /api/v2/roles— list rolesPOST /api/v2/roles— create roleGET /api/v2/applications— list applicationsPOST /api/v2/applications— create applicationGET /api/v2/organizations— list organizationsPOST /api/v2/organizations— create organizationGET /api/v2/connections— list connectionsPOST /api/v2/connections— create connection
auth0:
tenant: my-tenant
applications:
- client_id: my-app
client_secret: secret
name: My App
callbacks:
- http://localhost:3000/api/auth/callback
grant_types:
- authorization_code
- refresh_token
- client_credentials
users:
- email: dev@example.com
name: Developer
password: pass
roles:
- name: admin
connections:
- name: Username-Password-Authentication
strategy: auth0
apis:
- audience: https://api.example.test/
name: Example API