Certificate management · Checked 4 November 2026, 18:06 UTC.
Sectigo’s 3 November announcement says its GlobalSign and EJBCA connectors are available. They bring more external certificate authorities into Sectigo Certificate Manager (SCM), potentially reducing the number of separate management workflows.
The release date deserves a distinction: the official release notes list this support under CA Connector 3.6 and SCM 26.10, both dated 24 October. November 3 is the announcement date, not evidence of a new software release that day.
Which certificates are covered?
Sectigo’s support matrix names GlobalSign Atlas, with public DV, OV and EV SSL certificates. For EJBCA, it lists private SSL certificates. The matrix does not list client, device or code-signing certificate support for either connector. Teams should not interpret the broad product announcement as support for every certificate their CA can issue.
Integration limits that affect the plan
The installation guide specifies:
- EJBCA needs Connector 3.6, enabled REST and Web Service APIs, and profiles permitting immediate issuance. Manual approval is unsupported. Each local backend connects to one CA.
- Atlas needs API credentials plus mTLS. DV, OV and EV require separate backends; each credential fixes the issuing CA and template.
- The guide lists 64-bit Windows Server 2016, 2019 or 2022, appropriate SCM/CA permissions and outbound HTTPS connectivity.
What to verify before relying on it
An inventory also needs a clear scope: the CA scanning guide describes discovery of issued certificates that are neither expired nor revoked. That is not a complete historical issuance archive.
Our operational recommendation is to choose a representative certificate, confirm the account’s commercial entitlement, and test issuance, renewal, deployment and recovery in an authorized non-production environment. Check the resulting chain with the actual clients. Keep any required human approval in the design rather than removing it solely to accommodate a connector.
We reviewed the vendor documentation; we did not install or test these integrations. A successful connector setup should be followed by evidence that the certificate reaches the application and remains trusted there.