docs/documentation/platform/pki/ca/sectigo.mdx
Infisical can connect to Sectigo using the ACME-compatible CA integration to issue certificates back to your end-entities.
Sectigo Certificate Manager (SCM) supports the ACME protocol and requires External Account Binding (EAB) for all ACME registrations. You will need to obtain the ACME Directory URL, a Key Identifier (KID), and an HMAC Key from your Sectigo account before registering the ACME CA in Infisical.

On the account details page, copy the following values:
- **Server**: This is your ACME Directory URL (e.g., `https://acme.sectigo.com/v2/DV`).
- **Key ID**: Found under the **External Account Binding** section.
- **HMAC Key**: Found under the **External Account Binding** section.

- **Directory URL**: Paste the **Server** URL from Sectigo (e.g., `https://acme.sectigo.com/v2/DV`).
- **EAB Key Identifier (KID)**: Paste the **Key ID** from Sectigo.
- **EAB HMAC Key**: Paste the **HMAC Key** from Sectigo.
Now that your Sectigo CA is configured, set up the infrastructure to issue certificates:
<CardGroup cols={2}> <Card title="Certificate Profiles" icon="file-certificate" href="/documentation/platform/pki/settings/profiles"> Create a profile that references your Sectigo CA. </Card> <Card title="Applications" icon="grid-2" href="/documentation/platform/pki/applications/overview"> Create an Application, attach a profile, and configure enrollment. </Card> <Card title="Enrollment Methods" icon="arrow-right-to-arc" href="/documentation/platform/pki/applications/enrollment-methods/overview"> Choose how certificates are requested — API, ACME, EST, or SCEP. </Card> <Card title="Quick Start" icon="rocket" href="/documentation/platform/pki/quick-starts/issue-first-certificate"> Issue your first certificate end-to-end. </Card> </CardGroup>