How Sectigo ACME is sold
Sectigo offers ACME through its Certificate-as-a-Service (CaaS) platform. You usually buy it through a reseller or partner rather than directly, and it is a separate product from ordinary retail certificates: an existing certificate order cannot normally be turned into an ACME account.
What you receive after buying is:
- a directory URL, which depends on the certificate type,
- an EAB key ID and HMAC key to bind your ACME client to the account, and
- for OV, an organisation that has been validated in advance.
Sectigo’s documentation for DV issuance and OV, EV and QWAC issuance describes the partner side: the partner registers your account and passes you the server URL and EAB details. Directory URLs follow the form https://acme.sectigo.com/v2/DV or https://acme.sectigo.com/v2/OV, but use exactly the URL your provider gives you.
DV and OV
- DV certificates only prove control of the domain. You can issue as soon as your client is registered and passes a challenge.
- OV certificates also include your organisation. Sectigo validates the organisation first, and your ACME account must be registered against the OV directory and linked to that validation. Issuing before that is finished fails.
Both are 90-day certificates renewed by the client, not by you. The subscription itself has its own term, so renewing certificates and renewing the package are separate tasks.
Setting up a client
- Pick an ACME client that supports External Account Binding. Most do; our guide to ACME External Account Binding covers the flags for Certbot, acme.sh, lego and cert-manager.
- Register once with the directory URL, key ID and HMAC key, and back up the account the client creates.
- Choose a challenge. Wildcards need DNS-01, explained in wildcard certificates with ACME DNS-01.
- Issue one certificate, deploy it and check what the service serves.
- Confirm that automatic renewal is scheduled, and put the package end date in your calendar or tool.
Common problems
- Wrong directory for the product. DV credentials do not work on the OV directory and the other way around.
- OV not validated yet. Orders fail until the organisation validation is complete.
- A client without EAB support. Some appliances and control panels only support Let’s Encrypt. Check for custom directory and EAB support first.
- Package expiry. When the paid term ends, renewals stop, and a new package may come with new EAB credentials.
Where clm.mt fits
clm.mt has a Sectigo preset that takes the directory URL and EAB credentials, and warns before the package end date you enter. It is Preview: the ACME path is the same one we test with other CAs, but a live Sectigo package has not yet been part of our acceptance. See the integrations board for the current status.