mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-30 14:57:36 +00:00
zeekay
0ebffbd529
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
14 lines
895 B
Plaintext
14 lines
895 B
Plaintext
---
|
|
title: "Overview"
|
|
sidebarTitle: "Overview"
|
|
---
|
|
|
|
Before issuing and managing certificates with KMS, you'll need to configure a Certificate Authority (CA).
|
|
|
|
This is the trusted entity that signs and validates the X.509 certificates used to secure your end-entities.
|
|
|
|
KMS supports two categories of CAs:
|
|
|
|
- [Internal CA](/documentation/platform/pki/ca/private-ca): Internally operated root and intermediate CAs managed within KMS. This is useful if you need complete control over your PKI and are issuing certificates for private networks, internal services, or managed devices.
|
|
- [External CA](/documentation/platform/pki/ca/external-ca): Third-party public (e.g. Let's Encrypt, DigiCert) or private (e.g. AWS Private CA, HashiCorp Vault PKI, etc.) CAs that can be integrated with KMS. This is useful if you want to leverage existing PKI infrastructure or issue publicly trusted certificates.
|