| section | cre | ||||||
|---|---|---|---|---|---|---|---|
| date | Last Modified | ||||||
| title | Logging in with the CLI | ||||||
| metadata |
|
import { Aside, ClickToZoom } from "@components"
To deploy and manage workflows with the CRE CLI, you need to authenticate your CLI session with your CRE account. This guide walks you through the browser-based login process.
{/* prettier-ignore */}
If you need to authenticate without a browser (e.g., in a CI/CD pipeline), use [API key authentication](/cre/reference/cli/authentication#api-key-authentication) instead.- CRE CLI installed on your machine
- CRE account created
- Access to your authenticator app for two-factor authentication
Open your terminal and run the login command:
cre loginThis command will automatically open your default web browser to begin the authentication process.
If your browser doesn't open automatically, the CLI will display a URL that you can manually copy and paste into your browser.In the browser window that opens, enter the email address associated with your CRE account and click "Continue".
Enter your account password and click "Continue".
You'll be prompted to complete two-factor authentication based on the method you configured during account creation:
- If you set up an authenticator app: Open your authenticator app and enter the 6-digit one-time code it generates for your CRE account.
- If you set up biometric authentication: Use your fingerprint or face recognition as prompted by your device.
Example of entering a one-time code from an authenticator app:
Once authenticated, you'll see a confirmation message in your browser:
You can now close the browser window and return to your terminal. Your terminal will display:
Login completed successfullyYour CLI session is authenticated and ready to use.
In the terminal, the CLI may show “Fetching user context…” while it downloads your organization’s tenant configuration from the platform. It then writes ~/.cre/context.yaml (registry manifest: vault gateway URL, registries, secrets auth flows, and related fields). That file is separate from your credentials file (cre.yaml). For details and a sanitized example, see Tenant context cache.