Auth0 authentication method is missing documentation

@JQ105 good question! Looks like for the Auth0 authentication option on our REST API resource, we use “client credentials” grant_type, which is a client<-> server handshake that doesn’t require any user interaction. Specifically, the Auth0 option shown in the screenshot below only supports the Client Credentials use case documented in Auth0 docs: Client Credentials Flow and Call Your API Using the Client Credentials Flow

I've filed a request to our product team to rename the Auth0 option to be clearer that it’s only for the “Auth0 Client Credentials” flow. While I was at it, I requested whether there'd be a way to add a tooltip somewhere (perhaps on each of the fields above like "Auth0 Domain", "Auth0 Client ID", "Auth0 Client Secret") that points to the Auth0 docs containing where to locate this information. Appreciate the feedback that it is currently confusing as to which of Auth0's many authentication types is supported.

As for documentation, given the dozens and dozens of third party platforms that Retool integrates with, including auth providers, our docs team prefers that users reference the docs provided by that third party (in this case Auth0's own docs). This is because things could change on their end, and their docs should be considered the source of truth. Still, in-product we could be clearer with the nomenclature and tooltips.

In terms of the specific use case @Omer_Katz outlined above, it sounds like you're trying to use OAuth2 with Auth0. I believe you could solve the problem by selecting OAuth2.0 as the Authentication option instead of Auth0, and specifying the scopes you need. :thinking: Hope that helps as a possible workaround.