CLI
Authentication

CLI Authentication

The Onvera CLI supports multiple authentication methods. Choose the method that best fits your workflow.

Browser Login (Recommended)

Browser login is the default and recommended method. It opens your browser for authentication:

onvera auth login

How it works:

  1. CLI creates a login session
  2. Opens your browser to the Onvera login page
  3. You authenticate and approve CLI access
  4. CLI receives an API key and stores it locally

Example output:

Opening browser for authentication...
Waiting for approval...
✓ Authentication successful!
API key stored in ~/.config/onvera/config.json

API Key Authentication

Interactive Key Entry

Paste your API key interactively:

onvera auth login --key

The CLI will prompt you to paste your API key securely.

Direct Key Entry

Provide the API key directly:

onvera auth login --token onv_sk_live_...
ℹ️

API keys start with onv_sk_live_. You can create API keys in the Onvera dashboard (opens in a new tab).

Environment Variable

You can also set the API key as an environment variable:

export ONVERA_API_KEY=onv_sk_live_...

This bypasses stored credentials. Useful for CI/CD environments.

Logout

Clear stored credentials:

onvera auth logout

This removes the API key from local storage but does not revoke the key on the server.

Configuration Location

Credentials are stored in:

  • Linux/macOS: ~/.config/onvera/config.json
  • Windows: %APPDATA%\onvera\config.json

Troubleshooting

Browser doesn't open

If the browser doesn't open automatically:

  1. Check the terminal output for the login URL
  2. Copy and paste the URL into your browser manually
  3. Complete authentication in the browser

Authentication fails

If authentication fails:

API key expired

If your API key has expired:

  1. Create a new API key in the dashboard (opens in a new tab)
  2. Run onvera auth login --token <new-key>

Next Steps

After authentication:

InstallationCommands