For the complete documentation index, see llms.txt. This page is also available as Markdown.

Let's Encrypt

The Let’s Encrypt CA Connector enables CERTInext to integrate directly with Let’s Encrypt using the ACME (Automatic Certificate Management Environment) protocol for automated SSL/TLS certificate lifecycle management. Once configured, CERTInext can communicate securely with Let’s Encrypt services to automate certificate issuance, renewal, validation, and lifecycle tracking directly from the CERTInext platform.

This integration helps organizations simplify public SSL/TLS certificate management while leveraging Let’s Encrypt’s free and automated certificate services.

Typical use cases include:

  • Automated SSL/TLS certificate issuance

  • ACME-based certificate automation

  • Web server certificate management

  • Short-lived certificate renewals

  • Public website security automation

  • DevOps and cloud-native certificate provisioning

Accessing the Let’s Encrypt Connector

To configure a Let’s Encrypt connector:

  1. Navigate to Integrations → CA Connectors → Let’s Encrypt

  2. Click Create CA Connector

This opens the Let’s Encrypt connector configuration page where ACME connectivity and account details are configured.

Let’s Encrypt Connector Configuration Fields

The following fields are required when creating a Let’s Encrypt connector.

Name

Defines a unique name for the connector configuration.

Example:

This name is used internally within CERTInext to identify the integration.

ACME Environment

Specifies the Let’s Encrypt ACME environment to be used.

Available options include:

Production

Used for live certificate issuance from Let’s Encrypt’s production environment.

Certificates issued from this environment are publicly trusted and intended for real production workloads.

Staging

Used for testing and validation purposes.

The staging environment helps administrators validate automation workflows without hitting production rate limits. Certificates issued from staging are not publicly trusted.

It is recommended to use the Staging environment during initial configuration and testing.

Contact Email

Specifies the administrator or operational contact email address associated with the ACME account.

Example:

This email may be used by Let’s Encrypt for important notifications such as:

  • Expiry alerts

  • ACME account notices

  • Operational communications

Testing the Connector

After entering all required details:

  1. Click Test Connection

  2. CERTInext validates:

    • ACME endpoint connectivity

    • Let’s Encrypt environment access

    • Account registration capability

    • API communication availability

If the validation succeeds, the connector can be saved and used for certificate operations.

Certificate Operations Supported

Once configured, the Let’s Encrypt connector enables CERTInext to perform:

  • Automated certificate issuance

  • Domain validation workflows

  • ACME challenge handling

  • Certificate renewal

  • Certificate revocation

  • Lifecycle monitoring

  • Certificate inventory tracking

These operations are executed through secure ACME-based communication between CERTInext and Let’s Encrypt.

Domain Validation Support

The Let’s Encrypt connector supports automated domain validation using standard ACME validation methods, including:

  • DNS-based validation

  • HTTP-based validation

CERTInext can coordinate validation workflows using supported DNS connectors and automation capabilities.

Operational Flow

The typical certificate lifecycle workflow using the Let’s Encrypt connector is:

For automated environments, CERTInext can streamline the entire issuance and renewal lifecycle with minimal manual intervention.

Last updated