Deprecation of `enabled_clients` when using auth0-terraform

Get Help
,
1

Problem

Auth0 is deprecating the enabled_clients field on a connection object in the context of getting/updating connections, see deprecation note.
We see depnote events in the logstream for a production tenant, not tied to a terraform release.

Question

Does auth0-terraform use those deprecated calls to implement setting/reading enabled_clients on the Connection Resource? If so, when is a change to the new dedicated endpoints ( Welcome to Auth0 Docs - Auth0 Docs
and Welcome to Auth0 Docs - Auth0 Docs) planned?

We’re on v 1.34 of auth0-terraform and there is no mention of an update in the release notes for new versions.

3

Hi @sascha.picard1

Welcome to the Auth0 Community!

I understand that you are asking why the enabled_clients parameter is not available in the Terraform auth0_connection resource, even though it remains available in the Auth0 Management API.

The auth0_connection resource should be using the new Management API endpoints specified in the deprecation notes instead of the old ones.

Can you confirm that you experience issues in using the specific resource to read/update the enabled_clients values?

I will investigate internally in regards to the specific resource and confirm that they have been migrated to the new endpoints.

Kind Regards,
Nik

4

Hi Nik,

Sorry, I see that we’re still defining enabled_clients using the auth0_connection_clients.

However, I don’t see an enabled_clients (or similiar) option in Terraform Registry

Can you pls provide more guidance here? Can share TF code if needed.

5

Thank you for the added information!

The enabled_clients parameter was deprecated and removed from the Terraform Auth0 provider. After this deprecation took effect, the Terraform documentation was updated to introduce replacement resources for managing client connections.

Root Cause: The Terraform Auth0 provider deprecated the enabled_clients parameter for the auth0_connection resource to align with a broader API design change. However, the parameter remains available in the Auth0 Management API itself, creating a discrepancy between the two interfaces.

Solution: Use the dedicated Terraform resources to manage client connections instead of enabled_clients.

  1. Replace the enabled_clients parameter with the auth0_connection_clients resource to manage which clients are associated with a connection.

  2. Use the auth0_connection_client resource (singular) to manage individual client-connection associations if you need fine-grained control.

  3. Verify your Terraform configuration uses these resources instead of attempting to pass enabled_clients directly to the auth0_connection resource.

If you are using the Management API directly: The enabled_clients parameter is still available in the Auth0 Management API and can be used when creating or updating connections through API calls. This parameter is not deprecated in the API itself—only in the Terraform provider.

Important note: If you attempt to use enabled_clients with the Terraform provider and receive an error, you must use the auth0_connection_clients or auth0_connection_client resources instead. The Terraform provider no longer accepts this parameter.

Please follow up if you need further assistance with Terraform resource configuration.

Kind Regards,
Nik

6

Hi Nik,
I dug deeper and on Migrate Enabled Client Management to Dedicated Connection Endpoints I read

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.

This for Auth0 Terraform Provider: 1.29.0+.
Given that we are on a newer version, I don’t understand why we see the depnote.

Hence I am thankful for more clarification.

Best

Sascha