Auth0 Terraform Enabled Clients deprecation

Get Help
,
1

I received an email mentioning there’s a deprecation notice for the enabled_clients field found in the Auth0 Management API, and that one of my tenants had been using it.

After investigation, we found that the issue was from the auth0 terraform provider needing updating. After following the update guide, and updating the provider to version 1.29.0+, I am still seeing the deprecation notice in my log files, copied below. Can I get any help here? All steps from the guide had been followed.

{
“description”: “The enabled_clients field is deprecated when retrieving (GET) or updating (PATCH) connections and will stop being accessible or modifiable. Instead, use the dedicated client management endpoints (GET - /api/v2/connections/{id}/clients) and (PATCH - /api/v2/connections/{id}/clients).”,
“request”: {
“userAgent”: “Terraform-Provider-Auth0/1.29.0 (Go-Auth0-SDK/1.28.0; Terraform-SDK/2.36.1; Terraform/1.4.6)”,
“ip”: “…”,
“path”: “/api/v2/connections/{id}”,
“method”: “get”
},
“response”: {}
}

3

Hi @Danila19021

Welcome to the Auth0 Community!

You are asking why Auth0 still logs the enabled_clients deprecation warning after you upgraded the Auth0 Terraform Provider to version 1.29.0 or later and followed the migration guide. The key point is that the warning can still appear for any GET or PATCH call to /api/v2/connections/{id} while the tenant’s deprecation setting remains enabled, even after the Terraform provider migration is complete.

Root Cause: Auth0 generates this warning for any request to the /api/v2/connections/{id} endpoint when the deprecation setting is active on the tenant, and the warning can persist regardless of Software Development Kit or deployment tool upgrades.

You will need to:

  1. Confirm that the Auth0 Terraform Provider is running at version 1.29.0 or later, because versions earlier than 1.29.0 still rely on the deprecated enabled_clients behavior and can fail after the end-of-life date.
  2. Recognize that a GET request to /api/v2/connections/{id} can still trigger the deprecation warning even after the provider upgrade, because Auth0 documents that the warning is tied to endpoint usage while the tenant deprecation switch is active.
  3. Review the migration guidance in the Auth0 documentation on migrating enabled client management to dedicated connection endpoints to verify that all connection client management now uses /api/v2/connections/{id}/clients for client association changes.
  4. Check the log details for the userAgent and client_id fields, because Auth0 notes that some warnings can come from the Auth0 Dashboard, extensions, or platform services rather than from your Terraform workflow.
  5. Turn off the tenant’s deprecation switch if you want the warnings to stop appearing, because Auth0 states that the warnings persist as long as the deprecation setting remains active; Auth0 also recommends observing whether anything fails before the deprecation deadline.
  6. Monitor for actual failures rather than warnings alone, because the support guidance explains that the warning is informational until the legacy functionality reaches end of life.

Kind Regards,
Nik