Auth0 authentication option

[Bjorn_Hansen]

Im also curious about the Auth0 authentication option. Currently there is no mentioned of it on the API authentication docs: Configure API authentication | Retool Docs

It has fields for: Auth0 Domain, Client ID, and Client Secret but it's not clear which client it's expecting I use. Is this for an application, machine-to-machine, or Auth0 Management API? I don't see how I can use it to authenticate as a user using the usual Auth0 UI flow.

Why are you suggesting users use OAuth2.0 rather than the Auth0? Will it be deprecated soon?

[kbn]

@Bjorn_Hansen Sharing a related comment that hopefully sheds more light on your questions It seems like the suggestion to use our OAuth2.0 option is because it can support use cases that aren't supported by the specific type of Auth0 authentication provided (Auth0 Client Credentials).

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 [Screen Shot 2024-03-25 at 3.15.55 PM] I've filed a request to our prod…

[Tess]

We don't have plans to deprecate this option. Hope the extra context Kayla shared helps!