### Setting Environment Variables for Auth0 Provider (Client Secret) Source: https://registry.terraform.io/providers/auth0/auth0/latest/docs Set environment variables to configure the Auth0 provider with client secret authentication. This is a recommended practice to avoid hard-coding credentials. ```bash AUTH0_DOMAIN="" \ AUTH0_CLIENT_ID="" \ AUTH0_CLIENT_SECRET="" \ terraform plan ``` -------------------------------- ### Setting Environment Variables for Auth0 Provider (Private JWT) Source: https://registry.terraform.io/providers/auth0/auth0/latest/docs Set environment variables to configure the Auth0 provider with private key JWT authentication. This is a secure alternative to using client secrets directly. ```bash AUTH0_DOMAIN="" \ AUTH0_CLIENT_ID="" \ AUTH0_CLIENT_ASSERTION_PRIVATE_KEY="" \ AUTH0_CLIENT_ASSERTION_SIGNING_ALG="" \ terraform plan ``` -------------------------------- ### Auth0 Provider Configuration Source: https://registry.terraform.io/providers/auth0/auth0/latest/docs This snippet shows the basic configuration for the Auth0 provider using domain, client ID, and client secret. ```APIDOC ## Provider auth0 ### Description The Auth0 provider is used to interact with the Auth0 Management API in order to configure an Auth0 Tenant. It provides resources that allow you to create and manage various Auth0 entities. ### Example Usage ```terraform provider "auth0" { domain = "" client_id = "" client_secret = "" debug = "" } ``` ### Schema #### Optional * `api_token` (String) Your Auth0 management api access token. It can also be sourced from the `AUTH0_API_TOKEN` environment variable. It can be used instead of `client_id` + `client_secret`. If both are specified, `api_token` will be used over `client_id` + `client_secret` fields. * `audience` (String) Your Auth0 audience when using a custom domain. It can also be sourced from the `AUTH0_AUDIENCE` environment variable. * `cli_login` (Boolean) While toggled on, the API token gets fetched from the keyring for the given domain * `client_assertion_private_key` (String) The private key used to sign the client assertion JWT. It can also be sourced from the `AUTH0_CLIENT_ASSERTION_PRIVATE_KEY` environment variable. * `client_assertion_signing_alg` (String) The algorithm used to sign the client assertion JWT. It can also be sourced from the `AUTH0_CLIENT_ASSERTION_SIGNING_ALG` environment variable. * `client_id` (String) Your Auth0 client ID. It can also be sourced from the `AUTH0_CLIENT_ID` environment variable. * `client_secret` (String) Your Auth0 client secret. It can also be sourced from the `AUTH0_CLIENT_SECRET` environment variable. * `custom_domain_header` (String) When specified, this header is added to requests targeting a set of pre-defined whitelisted URLs Global setting overrides all resource specific `custom_domain_header` value * `debug` (Boolean) Enables HTTP request and response logging when TF_LOG=DEBUG is set. It can also be sourced from the `AUTH0_DEBUG` environment variable. * `domain` (String) Your Auth0 domain name. It can also be sourced from the `AUTH0_DOMAIN` environment variable. * `dynamic_credentials` (Boolean) Indicates whether credentials will be dynamically passed to the provider from other terraform resources. ### Environment Variables You can provide your credentials via the `AUTH0_DOMAIN`, `AUTH0_CLIENT_ID` and `AUTH0_CLIENT_SECRET` or `AUTH0_API_TOKEN` or `AUTH0_DOMAIN`, `AUTH0_CLIENT_ID`, `AUTH0_CLIENT_ASSERTION_PRIVATE_KEY` and `AUTH0_CLIENT_ASSERTION_SIGNING_ALG` environment variables, respectively. ### Example Usage with Client Secret ```bash AUTH0_DOMAIN="" \ AUTH0_CLIENT_ID="" \ AUTH0_CLIENT_SECRET="" \ terraform plan ``` ``` -------------------------------- ### Auth0 Provider Configuration with Private JWT Source: https://registry.terraform.io/providers/auth0/auth0/latest/docs This snippet demonstrates configuring the Auth0 provider using a client assertion private key for JWT authentication. ```APIDOC ## Provider auth0 ### Description The Auth0 provider is used to interact with the Auth0 Management API in order to configure an Auth0 Tenant. It provides resources that allow you to create and manage various Auth0 entities. ### Example Usage ```terraform provider "auth0" { domain = "" client_id = "" client_assertion_private_key = file("") client_assertion_signing_alg = "" debug = "" } ``` ### Schema #### Optional * `api_token` (String) Your Auth0 management api access token. It can also be sourced from the `AUTH0_API_TOKEN` environment variable. It can be used instead of `client_id` + `client_secret`. If both are specified, `api_token` will be used over `client_id` + `client_secret` fields. * `audience` (String) Your Auth0 audience when using a custom domain. It can also be sourced from the `AUTH0_AUDIENCE` environment variable. * `cli_login` (Boolean) While toggled on, the API token gets fetched from the keyring for the given domain * `client_assertion_private_key` (String) The private key used to sign the client assertion JWT. It can also be sourced from the `AUTH0_CLIENT_ASSERTION_PRIVATE_KEY` environment variable. * `client_assertion_signing_alg` (String) The algorithm used to sign the client assertion JWT. It can also be sourced from the `AUTH0_CLIENT_ASSERTION_SIGNING_ALG` environment variable. * `client_id` (String) Your Auth0 client ID. It can also be sourced from the `AUTH0_CLIENT_ID` environment variable. * `client_secret` (String) Your Auth0 client secret. It can also be sourced from the `AUTH0_CLIENT_SECRET` environment variable. * `custom_domain_header` (String) When specified, this header is added to requests targeting a set of pre-defined whitelisted URLs Global setting overrides all resource specific `custom_domain_header` value * `debug` (Boolean) Enables HTTP request and response logging when TF_LOG=DEBUG is set. It can also be sourced from the `AUTH0_DEBUG` environment variable. * `domain` (String) Your Auth0 domain name. It can also be sourced from the `AUTH0_DOMAIN` environment variable. * `dynamic_credentials` (Boolean) Indicates whether credentials will be dynamically passed to the provider from other terraform resources. ### Environment Variables You can provide your credentials via the `AUTH0_DOMAIN`, `AUTH0_CLIENT_ID` and `AUTH0_CLIENT_SECRET` or `AUTH0_API_TOKEN` or `AUTH0_DOMAIN`, `AUTH0_CLIENT_ID`, `AUTH0_CLIENT_ASSERTION_PRIVATE_KEY` and `AUTH0_CLIENT_ASSERTION_SIGNING_ALG` environment variables, respectively. ### Example Usage with Private JWT ```bash AUTH0_DOMAIN="" \ AUTH0_CLIENT_ID="" \ AUTH0_CLIENT_ASSERTION_PRIVATE_KEY="" \ AUTH0_CLIENT_ASSERTION_SIGNING_ALG="" \ terraform plan ``` ``` -------------------------------- ### Auth0 Provider Configuration with Client Secret Source: https://registry.terraform.io/providers/auth0/auth0/latest/docs Configure the Auth0 provider using domain, client ID, and client secret. This is a common method for authentication. ```terraform provider "auth0" { domain = "" client_id = "" client_secret = "" debug = "" } ``` -------------------------------- ### Auth0 Provider Configuration with No Explicit Credentials Source: https://registry.terraform.io/providers/auth0/auth0/latest/docs Configure the Auth0 provider without explicit credentials in the configuration file. This relies on environment variables or other implicit authentication methods. ```terraform provider "auth0" {} ``` -------------------------------- ### Auth0 Provider Configuration with Private Key JWT Source: https://registry.terraform.io/providers/auth0/auth0/latest/docs Configure the Auth0 provider using a private key for JWT assertion. This method is often used for service accounts or more secure integrations. ```terraform provider "auth0" { domain = "" client_id = "" client_assertion_private_key = file("") client_assertion_signing_alg = "" debug = "" } ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.