skip to content
Alvin Lucillo

Auth0 deprecation notice on enabled_clients

/ 1 min read

When you receive a deprecation notice on auth0, you need to plan for it in advance to avoid service interruption. One example is enabled_clients, which is a property that won’t be available for retrieval and modification via GET operations for /api/v2/connections and /api/v2/connections/{id}, and PATCH operations for /api/v2/connections/{id}, respectively. These endpoints are from auth0 management API. By July 13, 2026, the property won’t be available, and process (e.g., CI/CD, server, etc.) that rely on it might fail.

Before the end of life of that property, change your code to use these endpoints instead:

  1. Get enabled clients for a connection - https://{TENANT}.auth0.com/api/v2/connections/{id}/clients (see https://auth0.com/docs/api/management/v2/connections/get-connection-clients)
  2. Update enabled clients for a connection - https://{TENANT}.auth0.com/api/v2/connections/{id}/clients (see https://auth0.com/docs/api/management/v2/connections/patch-clients)

Resources:

  1. https://auth0.com/docs/troubleshoot/product-lifecycle/deprecations-and-migrations/migrate-dedicated-connection-endpoints
  2. https://auth0.com/docs/troubleshoot/product-lifecycle/deprecations-and-migrations#legacy-management-of-connection%E2%80%99s-enabled-clients