Skip to main content
Before you can access Anaconda services, you need to authenticate. The login process takes a few seconds.

​
Log in

This opens your browser for OAuth authentication. Once you authorize, the CLI generates an API key and stores it in the keyring:
C:\Users\<USER_NAME>\.anaconda\keyring
All future ana commands authenticate automatically using this stored key until it expires.
The activation URL is always displayed in the terminal. If your browser does not open automatically (SSH sessions, containers, headless servers), follow the on-screen link to complete authentication.

​
Options

​
Log in with an API key

If you already have an API key, you can skip the browser flow by passing it with the --api-key flag:
You are prompted to enter your key securely (input is hidden).

​
Non-interactive login for CI/CD

For pipelines, Docker builds, or other environments where no human is present, set the ANACONDA_AUTH_API_KEY environment variable instead of running ana login. All CLI commands use this key automatically when set. Store your API key in your CI provider’s secrets storage (such as GitHub Actions secrets or GitLab CI/CD variables) and expose it as ANACONDA_AUTH_API_KEY in your workflow. For Docker-specific guidance, see Authenticated Docker builds.
Never hardcode API keys in Dockerfiles or commit them to version control.

​
Display your stored API key

Prints the API key from the keyring. Useful for extracting your key to set as a CI secret:

​
Display account information

Displays your account information. Use the --json flag to output as JSON:

​
Log out

Removes your API key from the keyring. After logging out, a link is displayed to fully revoke the token on the web.

​
What’s next

With authentication in place, you can enable features like the main-x channel to configure your package managers.