Skip to content

Configuration

The Configuration module centralizes global platform settings including ACME profiles, connectors, email notifications, and enforcement policies.


ACME Profiles

ACME Profiles define how the platform integrates with ACME-compatible certificate authorities.

  • Profile ID
  • Directory URL
  • Trust Model (PRIVATE_PKI / PUBLIC_CA)
  • Environment (Production / Staging)
  • Validation Mode
  • EAB KID (External Account Binding)
  • Create ACME Profile
  • Edit Profile
  • Disable Profile
  • Rotate EAB Credentials
  • Delete Profile

ACME profiles are used during automated enrollment and renewal workflows.


Email Settings

Email notifications provide proactive operational alerts.

  • Enable / Disable Email Notifications
  • SMTP Host
  • SMTP Port
  • Username
  • Password
  • From Address
  • TLS (STARTTLS)
  • Default Test Recipient
  • Save Settings
  • Send Test Email
  • Certificate Expiring
  • Enrollment Failure
  • Deployment Failure
  • Agent Offline
  • Renewal Errors

Email configuration ensures operational visibility beyond the platform UI.


Configure integration with:

  • Certificate Authorities (Microsoft CA, Smallstep, etc.)
  • Agent Gateways
  • Certificate Stores
  • API endpoints
  • Authentication credentials
  • JSON configuration payload
  • Secret storage (vault-backed)
  • Refresh intervals
  • Retry policies

Connectors enable secure communication between SSL CLM and external systems.


Define organizational certificate governance rules.

  • Minimum key size
  • Allowed key algorithms
  • Maximum validity period
  • Required SAN entries
  • Restricted domains
  • Environment-based restrictions

Policies are validated during:

  • CSR submission
  • Certificate issuance
  • Renewal workflows
  • Deployment operations

  • Use Production vs Staging profiles appropriately
  • Rotate EAB and credentials periodically
  • Test SMTP configuration after changes
  • Apply strict policies in regulated environments

The Configuration module governs trust, automation, and enforcement across the entire SSL certificate lifecycle.