mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
zeekay
446e5ffd06
Comprehensive rip across the KMS UI + internal docs:
Frontend (47 .tsx + 5 .ts files):
- Infisical → Hanzo KMS
- INFISICAL_* env vars → KMS_*
- infisical-secret placeholder → hanzo-kms-secret
- infisicalSettings → hanzoKmsSettings
- 'infisical__provider-auth-token' → 'hanzo-kms__provider-auth-token'
(SecurityClient localStorage key)
- 'infisical loading indicator' alt text scrubbed
Docs (~10 .mdx files):
- All remaining brand mentions in platform/{pki,dynamic-secrets,pam}
integration guides → Hanzo KMS
- Image asset renamed:
images/platform/pki/sectigo/infisical-create-external-ca-acme.png
→ hanzo-kms-create-external-ca-acme.png
- Two doc references updated to point at the renamed asset
After this commit, the KMS admin UI shows zero upstream brand to
users. Verified by recursive grep: 0 .tsx / .ts / .mdx files contain
'Infisical' / 'INFISICAL' / 'infisical' in user-visible code paths.
Pairs with the prior hanzoai/docs scrub (commit 19c2a800a in
hanzoai/docs) and the recent IAM tenant-neutral rip.
44 lines
2.5 KiB
Plaintext
44 lines
2.5 KiB
Plaintext
---
|
|
title: "Sectigo"
|
|
description: "Learn how to connect Hanzo KMS to Sectigo to issue certificates via ACME."
|
|
---
|
|
|
|
## Concept
|
|
|
|
Hanzo KMS can connect to [Sectigo](https://www.sectigo.com/) using the [ACME-compatible CA integration](/documentation/platform/pki/ca/acme-ca) 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 Hanzo KMS.
|
|
|
|
## Guide to Connecting Hanzo KMS to Sectigo
|
|
|
|
<Steps>
|
|
<Step title="Retrieve ACME credentials from Sectigo">
|
|
Log in to your Sectigo Certificate Manager (SCM) portal and navigate to **Manage > ACME Accounts** in the left sidebar. Click **Manage** on the ACME account you want to use.
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
</Step>
|
|
<Step title="Create an External CA in Hanzo KMS">
|
|
Follow the steps in the [ACME-compatible CA integration](/documentation/platform/pki/ca/acme-ca) guide to create an External CA in Hanzo KMS with the **ACME** CA type. When filling out the form, use the values from Sectigo:
|
|
|
|
- **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.
|
|
|
|
|
|
</Step>
|
|
<Step title="Issue certificates">
|
|
Once the External CA is created, follow the rest of the [ACME-compatible CA integration](/documentation/platform/pki/ca/acme-ca) guide to create a Certificate Profile and start issuing certificates through Sectigo.
|
|
</Step>
|
|
</Steps>
|
|
|
|
<Note>
|
|
Sectigo ACME accounts are tied to specific domains configured in SCM. Ensure the domains you want to issue certificates for are added to your ACME account in Sectigo before requesting certificates through Hanzo KMS.
|
|
</Note>
|