Skip to main content
Auth0 provides Enterprise connections to authenticate users in an external, federated identity provider (IdP) such as Okta, Microsoft Entra ID, Google Workspace, and others. A configured connection will include protocol-specific settings for integrating single sign-in (SSO), user provisioning, and logout integrations with the external IDP, as well as private settings that govern how the connection interacts with Auth0’s Universal Login and Organizations features. The Connection Profile (CP) enables Auth0 developers to specify how the private settings of an Auth0 connection should be configured when created by third parties

How it works

  • Profile Definition: An administrator creates a Connection Profile that defines the property values that should be written to the connection whenever they are created using one of Auth0 delegated administration features.
  • Flexible Scope: Profiles are linked to Self-Service Enterprise Configuration and Okta Express Configuration flows today but are designed for broader reuse, covering provisioning, onboarding, entitlement management, and future Auth0 capabilities.

Connection Profile properties

A Connection Profile is a JSON object that supports these configurable properties, which are applied to all newly created connections.

Example Connection Profile

Create and manage Connection Profiles

A Connection Profile is automatically generated when using the Express Configuration feature with Okta. In addition, create and manage Connection Profiles using the Auth0 Management API.

Configure with Management API

To use the Management API, you need to get a Management API access token. To manage Connection Profiles, the following Management API endpoints are available:
  • POST /api/v2/connection-profiles
  • GET /api/v2/connection-profiles
  • PATCH /api/v2/connection-profiles/{id}
  • GET /api/v2/connection-profiles/{id}
  • GET /api/v2/connection-profiles/templates

Learn More