Issue a Certificate
The CLM supports multiple Certificate Authorities (CAs). The issuance flow consists of 3 steps in the CSR wizard — Step 1 and Step 3 are the same for all CAs. Only Step 2 varies depending on the chosen CA.
Step 1 — Identification (same for all CAs)
Go to CSR in the sidebar menu and click New Request.
| Field | Description |
|---|---|
| Certificate Name | Name to identify the certificate in the CLM |
| Certificate Type | SSL/TLS (filled automatically) |
| Domain / Common Name | Main domain, e.g. app.yourcompany.com |
| Alternative Names / SANs | Additional domains separated by commas (optional) |
| Key Size | Key size — 2048, 3072, or 4096 bits |
Step 2 — CA and Configuration (specific per CA)
See the Issuance flow for the end-to-end walkthrough, or go straight to your CA's guide:
- Issue with Let's Encrypt — free DV certificates, automatic validation
- Issue with Sectigo (ACME) — certificates via ACME, domain delegated in the SCM
- Issue with DigiCert (ACME) — certificates via ACME on CertCentral
- Issue with GlobalSign (ACME) — certificates via ACME on Atlas
- Issue with Google Trust Services (ACME) — certificates via ACME, registered through the generic card
- Issue with ZeroSSL (ACME) — certificates via ACME, registered through the generic card
- Issue with SSL.com (ACME) — certificates via ACME, explicit CAA required
- Issue with another CA (ACME) — any ACME-compatible CA without a dedicated guide
- Issue with DigiCert — OV/EV certificates via native API, corporate validation
- Issue with Microsoft AD CS — internal certificates via on-premises Enterprise CA
Step 3 — Review (same for all CAs)
Check all the settings filled in the previous steps and click Submit request.
After submission, the CLM processes the request with the selected CA. Once the certificate is successfully issued, the status changes to Issued and the View Certificate button becomes available to access the certificate directly in Certificates.