Productivity / Enterprise
Auth0 OAuth
Auth0 endpoints, audiences, connections, and token claims are tenant-specific; the workflow must start from the tenant issuer URL.
Manual / specialised flowProvider docs
What this workflow can do
- Manual provider checklist
- Provider-specific inputs
- Generic OAuth form
Before starting
- Auth0 tenant domain or custom domain
- clientId and client authentication method
- redirectUri
- audience, scopes, and optional connection
- authorization code
Result handling
- Use the checklist to complete provider-specific setup outside the generic form.
- Anonymous OAuth Hub workflows do not store secrets, tokens, or provider payloads.
- 01UnderstandReview why this provider needs a specialized setup path.
- 02CollectGather the required provider-specific fields.
- 03Run setupComplete the provider flow outside the generic OAuth form.
- 04ValidateUse the checklist to confirm token and metadata handling.
Specialised flow
Manual provider setup
Auth0 endpoints, audiences, connections, and token claims are tenant-specific; the workflow must start from the tenant issuer URL.
Required inputs
- Auth0 tenant domain or custom domain
- clientId and client authentication method
- redirectUri
- audience, scopes, and optional connection
- authorization code
Troubleshooting
- Use the tenant's .well-known/openid-configuration document rather than hardcoding endpoints.
- Refresh tokens require offline_access plus the appropriate application and API settings.
Provider checklist
- Enter and validate the Auth0 issuer or tenant domain.
- Discover authorization, token, userinfo, and JWKS endpoints.
- Build Authorization Code or PKCE parameters for the registered application type.
- Validate issuer, audience, nonce, state, and ID-token signature.