> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/certificate-authorities-and-trust-stores/supported-public-certifying-authorities/sectigo.md).
# Sectigo
The Sectigo CA Connector enables CERTInext to integrate directly with Sectigo Certificate Manager for automated certificate lifecycle management. Once configured, CERTInext can communicate securely with Sectigo APIs to perform certificate issuance, renewal, revocation, reissuance, and validation workflows directly from the CERTInext platform.
This integration helps organizations centralize certificate operations while leveraging Sectigo’s publicly trusted SSL/TLS certificate services.
## Accessing the Sectigo Connector
To configure a Sectigo connector:
1. Navigate to **Integrations → CA Connectors → Sectigo**
2. Click **Create CA Connector**
This opens the Sectigo connector configuration page where API connectivity and authentication details are configured.
## Sectigo Connector Configuration Fields
The following fields are required when creating a Sectigo connector.
### Name
Defines a unique name for the connector configuration.
Example:
```
Sectigo Production Connector
```
This name is used internally within CERTInext to identify the integration.
### Sectigo API Base URL
Specifies the base API endpoint for Sectigo Certificate Manager.
Example:
```
https://cert-manager.com/api
```
This URL is provided by Sectigo and is used for all API communication between CERTInext and Sectigo.
### Client ID
The API Client ID issued by Sectigo for API authentication.
This identifier is associated with the organization’s Sectigo Certificate Manager account and is required for secure API access.
### Client Secret
The API Client Secret associated with the Client ID.
This credential is securely stored and used by CERTInext to authenticate API requests with Sectigo.
> Ensure the Client Secret is protected and accessible only to authorized administrators.
### Customer URI
Specifies the Sectigo customer-specific URI or tenant identifier.
Example:
```
myorganization
```
This value helps CERTInext route API requests to the correct Sectigo account environment.
### Organization ID
Defines the Sectigo organization identifier associated with certificate issuance operations.
This value is typically provided by Sectigo during onboarding or API enablement.
### Certificate Validity
Defines the default certificate validity period used during issuance requests.
Example:
```
365
```
The validity value is typically specified in days and must align with Sectigo-supported certificate policies and industry regulations.
## Testing the Connector
After entering all required details:
1. Click **Test Connection**
2. CERTInext validates:
* API connectivity
* Authentication credentials
* Organization access
* Sectigo API response availability
If the validation succeeds, the connector can be saved and used for certificate operations.
## Certificate Operations Supported
Once configured, the Sectigo connector enables CERTInext to perform:
* Certificate issuance
* Domain validation workflows
* Certificate renewal
* Revocation requests
* Certificate reissuance
* Order status synchronization
* Certificate inventory tracking
These operations are executed through secure API communication between CERTInext and Sectigo.
## Certificate Operations Supported
Once configured, the Sectigo connector enables CERTInext to perform:
* Certificate issuance
* Domain validation workflows
* Certificate renewal
* Revocation requests
* Certificate reissuance
* Order status synchronization
* Certificate inventory tracking
These operations are executed through secure API communication between CERTInext and Sectigo.
## Operational Flow
The typical certificate lifecycle workflow using the Sectigo connector is:
```
CERTInext → Sectigo API → Validation → Certificate Issuance → Lifecycle Tracking
```
For domain-validated certificates, CERTInext can also coordinate DNS-based validation workflows when integrated with supported DNS connectors.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.certinext.io/documentation/certificate-authorities-and-trust-stores/supported-public-certifying-authorities/sectigo.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.