Unsupported Connection Strategy: oauth1

[alanc10n]

Checklist

• I have looked into the README and have not found a suitable solution or answer.
• I have looked into the documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have upgraded to the latest version of this provider and the issue still persists.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

In updating from 0.50.2 to 1.1.2, I'm getting an error on a connection as follows:

Error: Unsupported Connection Strategy
│ 
│   with auth0_connection.garmin-connect,
│   on connections.tf line 218, in resource "auth0_connection" "garmin-connect":
│  218:   strategy = "oauth1"
│ 
│ Raise an issue at https://github.com/auth0/terraform-provider-auth0/issues/new in order to have the following connection strategy supported: "oauth1"

This connection was working fine until the provider update; the resource definition is this:

 resource "auth0_connection" "garmin-connect" {
  name     = "garmin-connect"
  strategy = "oauth1"
}

I attempted to remove the connection from state and re-import, which also yields an error about unsupported strategy.

Expectation

oauth1 is accepted as a strategy, since it's been in the past and I see no documentation about it being removed.

Reproduction

Create the above resource definition

Auth0 Terraform Provider version

1.1.2

Terraform version

1.7.3

[alanc10n]

It's perhaps worth noting that removing the resource from state and trying to create a data source for it instead has the same issue. I took a quick look at the source and I see where strategies are defined, and oauth1 is part of the list, so it's not clear at a glance what's going wrong.

[duedares-rvj]

Hello!

Sincere apologies for such a delayed response.
We spoke to the API team with regards to the support of oauth1 as a valid connection strategy.

It has been agreed that we want to move away from OAuth1, but presently neither the API nor the documentation has been updated to reflect this stance. This may be because several social connections still depend on OAuth1, including:
Evernote, FitBit, Flickr, Twitter

We'd like to encourage the use of a newer strategy and move away from using oauth1

Let us know what you think about it.
Rest assured, the responses shall be sooner this time :)

[alanc10n]

What do I think about it? First, as you point out, it's not the Auth0 user's choice but rather the third-party service they're integrating with that determines what connection strategy is used. In my case, Garmin is the third-party service that only supports OAuth1. Second, this has been broken for a year while OAuth1 connections have still officially been supported, so until they've been properly deprecated and reached end of life, I'd expect this strategy to continue to be supported in the official Terraform provider. Our account team hasn't said anything about OAuth1 going away, so I'd guess that this change is not going to happen any time soon. And again, this was working fine until a provider update broke it.