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.
47 lines
2.7 KiB
Plaintext
47 lines
2.7 KiB
Plaintext
---
|
|
title: "DigiCert"
|
|
description: "Learn how to connect KMS to DigiCert to issue certificates."
|
|
---
|
|
|
|
## Concept
|
|
|
|
KMS can connect to [DigiCert](https://www.digicert.com/) using the [ACME-compatible CA integration](/documentation/platform/pki/ca/acme-ca) to issue certificates back to your end-entities.
|
|
|
|
## Guide to Connecting KMS to DigiCert CA
|
|
|
|
To connect KMS to DigiCert, follow the steps in the [ACME-compatible CA integration](/documentation/platform/pki/ca/acme-ca) guide but use the DigiCert **ACME Directory URL**: `https://acme.digicert.com/v2/acme/directory`.
|
|
|
|
DigiCert requires **External Account Binding (EAB)** for all ACME registrations. You will need to obtain both a Key Identifier (KID) and an HMAC Key from your DigiCert account before registering the ACME CA in KMS.
|
|
|
|
|
|
|
|
In the modal that appears, configure the following options:
|
|
- **Name**: A friendly name for the credential set.
|
|
- **Product**: The certificate product to use.
|
|
- **Division**: The division to associate with issued certificates.
|
|
- **Organization**: Required for OV/EV certificates.
|
|
- **Validity period**: The certificate validity duration.
|
|
|
|
Click **Add ACME Directory URL** to generate your credentials. A modal will display the generated credentials. Copy the following values:
|
|
- **ACME Directory URL**: A unique URL generated for your ACME requests.
|
|
- **Key Identifier (KID)**: Identifies your CertCentral account.
|
|
- **HMAC Key**: Used for authentication and encryption.
|
|
|
|
<Note>
|
|
These credentials are **only displayed once**. Make sure to copy and save them in a secure location before dismissing the modal. If you lose your credentials, you will need to revoke them and generate new ones.
|
|
</Note>
|
|
</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 DigiCert:
|
|
|
|
- **Directory URL**: Paste the **ACME Directory URL** from DigiCert.
|
|
- **EAB Key Identifier (KID)**: Paste the **Key Identifier** from DigiCert.
|
|
- **EAB HMAC Key**: Paste the **HMAC Key** from DigiCert.
|
|
|
|
|
|
</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 DigiCert.
|
|
</Step>
|
|
</Steps>
|