Skip to main content
The Auth0 connector integrates the Maverics Orchestrator with Auth0 by Okta — enabling OIDC-based single sign-on for applications that authenticate against Auth0 tenants.
Console terminology: In the Maverics Console, this section is called Identity Fabric. The YAML configuration uses the connectors key to define identity provider integrations.

​
Overview

The Auth0 connector uses OpenID Connect to federate authentication with Auth0. It uses type: auth0 in the connector configuration and supports standard OIDC flows — designed for organizations that use Auth0 as their identity platform, whether for customer-facing (CIAM) or workforce identity scenarios. The connector can also facilitate Auth0 tenant migrations and multi-IdP orchestration.

​
Use Cases

  • Auth0 SSO federation — Extend Auth0 authentication to legacy applications that don’t support OIDC natively
  • Auth0 tenant migration — Gradually migrate users between Auth0 tenants without downtime
  • Combining Auth0 with enterprise IdPs — Orchestrate authentication across Auth0 and enterprise identity providers like Azure AD or Okta

​
Configuration

Console UI documentation is coming soon. This section will walk you through configuring this component using the Maverics Console’s visual interface, including step-by-step screenshots and field descriptions.
Auth0 configuration screen in Maverics Console

​
Configuration Reference

KeyTypeRequiredDescription
namestringYesUnique connector identifier referenced in app policies
typestringYesMust be auth0
oidcWellKnownURLstringYesOIDC discovery endpoint URL (Auth0 tenant domain)
oauthClientIDstringYesOAuth 2.0 client ID from the Auth0 dashboard
oauthClientSecretstringYesOAuth 2.0 client secret (use secret reference syntax)
oauthRedirectURLstringYesCallback URL registered with the Auth0 application
scopesstringNoSpace-separated OAuth scopes (default: openid profile email)
oauthExtraParamsmapNoAdditional query parameters for the authorization request
tlsstringNoNamed TLS profile for provider communication
For the complete field reference including health checks, offline access, and PKCE settings, see Identity Fabric.

​
Troubleshooting

  • Verify the oidcWellKnownURL is accessible from the Orchestrator host — ensure the Auth0 domain is correct (e.g., your-tenant.auth0.com or custom domain)
  • Ensure the oauthRedirectURL matches exactly what is registered in the Auth0 application under Allowed Callback URLs
  • Check that the client secret reference resolves correctly via your secret provider

Identity Fabric

Overview of all identity providers

Okta

OIDC connector for Okta

Custom OIDC

Generic OpenID Connect connector

Continuity

Failover connector for IdP high availability