Authentication

The Doover CLI requires authentication to interact with the Doover platform. There are two primary authentication methods: interactive login for development and token-based authentication for CI/CD pipelines.

The doover login command provides an interactive way to authenticate with your Doover account using username and password.

doover login

You will be prompted for:

$ doover login
Doover username: myuser@example.com
Doover password: ********
Base API URL: https://my.doover.com
Profile name: default
Login successful.

You can also provide credentials as command-line options:

doover login \
  --username myuser@example.com \
  --password mypassword \
  --base-url https://my.doover.com \
  --profile-name production

For CI/CD pipelines and automated workflows, use doover configure-token to set up authentication with a long-lived API token.

doover configure-token

You will be prompted for:

$ doover configure-token
API Token: your-api-token-here
Agent ID: abc123
Base API URL: https://my.doover.com
Profile name: ci-pipeline
Token expiry (in days): 365
Successfully configured doover credentials.

doover configure-token \
  --token your-api-token \
  --agent-id abc123 \
  --base-url https://my.doover.com \
  --profile ci-pipeline \
  --expiry 365

API tokens can be generated from the Doover web interface:

1. Log in to the Doover platform
2. Navigate to your account settings
3. Go to the API tokens section
4. Generate a new token with the required permissions

The CLI supports multiple configuration profiles, allowing you to switch between different accounts or environments.

• Credentials are stored per profile
• The default profile is used when no profile is specified
• You can create profiles for different environments (development, staging, production)

Most commands accept a --profile option:

doover channel get my-channel --profile production

Configuration is stored by pydoover's ConfigManager. Each profile entry contains:

• Username and password (for login-based auth)
• API token and expiry (for token-based auth)
• Base URL
• Default agent ID

For CI/CD environments, you can configure authentication using environment variables instead of stored profiles.

# GitHub Actions example
env:
  DOOVER_API_TOKEN: ${{ secrets.DOOVER_API_TOKEN }}
  DOOVER_API_BASE_URL: https://my.doover.com

steps:
  - name: Deploy to Doover
    run: doover app publish --skip-container

# Shell script example
export DOOVER_API_TOKEN="your-token-here"
export DOOVER_API_BASE_URL="https://my.doover.com"
doover app publish

When working with multiple Doover environments (development, staging, production), create separate profiles:

# Configure development environment
doover login --profile dev --base-url https://dev.doover.com

# Configure staging environment
doover configure-token --profile staging --base-url https://staging.d.doover.com

# Configure production environment
doover configure-token --profile prod --base-url https://my.doover.com

Then use the --profile option with commands:

# Deploy to staging
doover app publish --profile staging

# Check channels in production
doover channel get my-channel --profile prod

If you see "Login failed. Please try again.", verify:

• Your username and password are correct
• The base URL is accessible
• Your account has the necessary permissions

Enable debug mode for more details:

doover --debug login

Common errors when configuring tokens:

When configuring a profile that already exists:

$ doover configure-token --profile default
There's already a config entry with this profile. Do you want to overwrite it? [y/N]

Confirm with y to overwrite, or use a different profile name.