Certificate lifecycle

Sectigo SCM Certificate Automation

Keep your existing Sectigo SCM account while automating requests, renewal, deployment and verification in SSLNexus.

Use the assigned SCM interface

The connector supports REST Enrollment and SCM Admin REST v2 as explicit configuration choices. Use the full tenant API URL and authentication assigned to your account; SSLNexus does not infer compatibility from the SCM product name.

Preserve the proven enrollment flow

REST Enrollment with OAuth is the established operationally qualified workflow. Tokens are obtained fresh for each CA operation. The journal preserves the CSR and request identity when work is pending or interrupted.

Match newer modes to your tenant

Admin v2 supports configured OAuth, password-header or certificate-login authentication. These modes have automated fixture coverage; live qualification is separate from the proven REST Enrollment workflow. Native SCM renewal-by-ID and legacy Admin v1 are not implied.

Finish the lifecycle on the target

After the CA returns the certificate, SSLNexus uses the selected application deployment path and records verification. A CA credential does not grant access to arbitrary deployment targets.

Plan your rollout

Start with one authorised target, test certificate acquisition and deployment, and confirm the resulting certificate is in use. Feature availability follows your installed release and active licence. The seven-day trial provides a way to evaluate the relevant workflow.