Migrate Enabled Client Management to Dedicated Connection Endpoints

Learn how to update your Auth0 connection configuration from using the enabled_clients field to dedicated connection endpoints.

Auth0 is deprecating the enabled_clients field from Management API’s Get All Connections, Get Connections, and Update a Connection. Auth0 customers can retrieve enabled clients on a connection by using the Get enabled clients for a connection endpoint. To update clients already established on a connection, use the Update enabled clients for a connection.

To prepare for this change and ensure your integrations continue to function smoothly, review the steps below to verify your affected status and migrate to the new endpoints.

To learn more about migration timelines, review the entry on Deprecations and Migrations.

Verify affected tenants

Private Cloud tenant administrators can follow these instructions if their Private Cloud deployment is version v202608 or later. To learn more about the Private Cloud deployments versions, read How to Check the Auth0 Private Cloud’s Release Number and Deployment Date.

You can use the Auth0 Dashboard to confirm whether a tenant is allowed access to the deprecated functionality and requires migration.

1. Navigate to Auth0 Dashboard > Tenant Settings > Advanced.
2. Under Migrations, review the Legacy Management of Connection’s Enabled Clients toggle.
   • Toggle is on: Your tenant allows access to the deprecated field when retrieving and updating connections, and you must migrate before the deadline.
   • Toggle is off: No further action is required.

Identify affected integrations

• Public Cloud tenants started to receive these deprecation notices in the first half of February 2026.
• Private Cloud tenants started to receive these deprecation notices when their Private Cloud deployments reached the v202608 version.

To determine which applications and integrations use the deprecated endpoints, review the tenant logs for deprecation notices. To learn more, read Check for Deprecation Errors.

Use the following query to search for notices specific to this deprecation:

type:depnote AND description:Legacy\ Management\ of\ Connection's\ Enabled\ Clients*

Review the query result for the client_id field to identify the potentially affected applications.

Some Auth0 platform services and extensions can cause deprecation notices in tenant logs:

• If the client_id field is empty, the notice originated from an extension.
• If the value does not match any of the tenant’s client applications, the notice originated from a platform service, and it can be ignored.

In addition, the presence of a deprecation notice for a specific client application does not necessarily indicate that the application is affected. For example, if one of your applications retrieves GET connection information, including the deprecated enabled_clients field, but does not process the field returned in the response, the scheduled deprecation of the field has no impact.

Review extensions usage

The following extensions can trigger deprecation notices in tenant logs:

• User Import/Export: This extension does not use the deprecated endpoints. These are false positive deprecation notices because the extension retrieves connection information.
• Custom Social Connections: This extension uses the deprecated endpoints and will experience issues and trigger deprecation notices.

These extensions are superseded by Auth0 Dashboard functionality that addresses their use cases and no longer receive updates.

• Use the Bulk User Import / Export Dashboard feature to replace the User Import/Export extension.
• Use the Social Identity Providers Dashboard feature to replace the Custom Social Connections extension.

Update your integrations

For applications and integrations using the impacted connection endpoints to retrieve (GET) or update (PATCH) the enabled_clients field, you must modify them to use the dedicated client management endpoints:

• To Read: Get enabled clients for a connection.
• To Write: Update enabled clients for a connection.

Update SDKs and Tools

The following SDKs and tools versions support the new endpoints:

• node-auth0: 4.25.0+
• go-auth0: 1.21.0+
• auth0-java: 2.21.0+
• auth0-python: 5.1.0+
• auth0.net: 7.38.0+
• Auth0 Deploy CLI: 8.27.0+
• Auth0 Terraform Provider: 1.29.0+

The Auth0 Deploy CLI / Auth0 Terraform Provider do not require changes to how connections and respective clients are represented in their data model. You must use the latest available version to guarantee the tool uses the dedicated endpoints.

The Ruby and PHP Management API SDKs are pending updates.

Opt-Out (Finalize Migration)

Once you ensure that integrations no longer depend on the deprecated behavior, you should configure the tenant to explicitly opt out.

• Why Opt-Out Early? This allows you to control the exact timeline at which a given tenant switches to the new behavior. In the event of any unexpected situation, you can quickly revert the toggle to restore the original behavior.
• How to Opt-Out: Navigate to Auth0 Dashboard > Tenant Settings > Advanced. Under Migrations, toggle off the Legacy Management of Connection’s Enabled Clients option.