Skip to main content

Customize your configuration settings

Specify a custom configuration file location as a persistent environment variable or as a command-line instruction when performing a service or ACME operation.

Configuration settings precedence

When applying configuration settings from multiple sources, settings are applied in this order (first to last priority):

  1. Command-line flags

  2. Local environment variables (ACME_CONFIG_FILE)

  3. Configuration file (specified in the default dc-acme.toml or a custom configuration file)

  4. System defaults

Define an environment variable

Tell your server where to store and retrieve CertCentral automation agent configuration settings.

export ACME_CONFIG_FILE="/path/to/custom/dc-acme.toml"

Create and use a custom file location

Specify a file location for the CertCentral automation agent to call and use.

# Create a custom configuration file
dc-acme --defaults > /path/to/custom.toml

# Use the custom configuration file
dc-acme request enroll --config /path/to/custom.toml --cn example.com

Enter configuration settings with ACME operations

Give the CertCentral automation agent one-time instructions when you submit requests at the command line.

# No configuration file - use CLI flags (example)
dc-acme request enroll \
  --directory-url "https://one.digicert.com/mpki/api/v1/acme/v2/directory" \
  --email "admin@example.com" \
  --eab-key "your-key" \
  --eab-hmac "your-hmac" \
  --cn "example.com"
In diesem Abschnitt: