Remote Nodes Authentication

Configure authentication for connecting to remote Dagu instances.

Configuration

YAML Configuration

# ~/.config/dagu/config.yaml
remoteNodes:
  - name: production
    apiBaseURL: https://prod.example.com/api/v2
    isBasicAuth: true
    basicAuthUsername: admin
    basicAuthPassword: prod-password
    
  - name: staging
    apiBaseURL: https://staging.example.com/api/v2
    isAuthToken: true
    authToken: staging-api-token
    
  - name: development
    apiBaseURL: http://dev.example.com:8080/api/v2
    # No auth configured - anonymous access

Environment Variables

Remote nodes must be configured in YAML. Environment variables are not supported for remote node configuration.

Authentication Types

Basic Authentication

remoteNodes:
  - name: remote1
    apiBaseURL: https://remote1.example.com/api/v2
    isBasicAuth: true
    basicAuthUsername: admin
    basicAuthPassword: secure-password

Token Authentication

remoteNodes:
  - name: remote2
    apiBaseURL: https://remote2.example.com/api/v2
    isAuthToken: true
    authToken: api-token-for-remote2

No Authentication

remoteNodes:
  - name: local-dev
    apiBaseURL: http://localhost:8081/api/v2
    # No auth fields - anonymous access

TLS Options

Skip TLS Verification

remoteNodes:
  - name: self-signed
    apiBaseURL: https://internal.example.com/api/v2
    skipTLSVerify: true
    isAuthToken: true
    authToken: token

Usage

Remote nodes appear in the Dagu UI and can be accessed through the interface. Each remote node maintains its own:

• DAG definitions
• Execution history
• Logs
• Status

Notes

• Each remote node can use different authentication
• Remote nodes are read-only from the main instance
• Authentication credentials are stored in the config file
• Use strong passwords and tokens for production
• Consider using TLS for all remote connections