> ## Documentation Index
> Fetch the complete documentation index at: https://auth0.com/llms.txt
> Use this file to discover all available pages before exploring further.

> Learn about the different methods of authenticating the Auth0 Deploy CLI with your tenant.

# Authenticate with your Tenant

There are three supported methods of authenticating the Auth0 Deploy CLI with your tenant.

## Client credentials

[Client credentials](/docs/get-started/authentication-and-authorization-flow/client-credentials-flow) authentication requires you provide a <Tooltip tip="Client ID: Identification value given to your registered resource from Auth0." cta="View Glossary" href="/docs/glossary?term=client+ID">client ID</Tooltip> and <Tooltip tip="Client ID: Identification value given to your registered resource from Auth0." cta="View Glossary" href="/docs/glossary?term=client+secret">client secret</Tooltip> pair directly to the application. This option is straightforward and enables the quickest path to setup for the tool.

To configure client credentials authentication, set the the following fields in your [configuration file](/docs/deploy-monitor/deploy-cli-tool/configure-the-deploy-cli):

| Field                 | Value                                    |
| --------------------- | ---------------------------------------- |
| `AUTH0_CLIENT_ID`     | Client ID of your Auth0 application.     |
| `AUTH0_CLIENT_SECRET` | Client secret of your Auth0 application. |

## Private key JWT

[Private key JWT](/docs/get-started/applications/configure-private-key-jwt) authentication requires you configure a private key for the application and a public key for the remote tenant. This option is ideal if do not want to store credentials remotely on Auth0.

To configure private key <Tooltip tip="JSON Web Token (JWT): Standard ID Token format (and often Access Token format) used to represent claims securely between two parties." cta="View Glossary" href="/docs/glossary?term=JWT">JWT</Tooltip> authentication, set the following fields in your [configuration file](/docs/deploy-monitor/deploy-cli-tool/configure-the-deploy-cli):

| Field                            | Value                                                     |
| -------------------------------- | --------------------------------------------------------- |
| `AUTH0_CLIENT_SIGNING_KEY_PATH`  | Relative path to the JWT signing key certificate.         |
| `AUTH0_CLIENT_SIGNING_ALGORITHM` | Optional. JWT signing algorithm used for the certificate. |

## Access token

[Access token](/docs/secure/tokens/access-tokens/management-api-access-tokens/get-management-api-access-tokens-for-production) authentication requires you provide an Auth0 <Tooltip tip="Management API: A product to allow customers to perform administrative tasks." cta="View Glossary" href="/docs/glossary?term=Management+API">Management API</Tooltip> <Tooltip tip="Management API: A product to allow customers to perform administrative tasks." cta="View Glossary" href="/docs/glossary?term=access+token">access token</Tooltip> directly to the application. This option puts more responsibility on developers but can enable flexible and specific workflows when necessary.

To configure access token authentication, pass a Management API Auth0 access token through the `AUTH0_ACCESS_TOKEN` [environment variable](/docs/deploy-monitor/deploy-cli-tool/configure-the-deploy-cli).