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
18 lines
1.4 KiB
Plaintext
18 lines
1.4 KiB
Plaintext
---
|
|
title: "Overview"
|
|
sidebarTitle: "Overview"
|
|
---
|
|
|
|
To issue a certificate with KMS, you create a certificate profile and a certificate policy to go along with it. You then issue a certificate against
|
|
a specific profile depending on the enrollment method associated with it.
|
|
|
|
There are four components to understand:
|
|
|
|
- [Certificate Profile](/documentation/platform/pki/certificates/profiles): A configuration set specifying how certificates should be issued under that profile including the [issuing CA](/documentation/platform/pki/ca/overview), a certificate policy, and the [enrollment method](/documentation/platform/pki/enrollment-methods/overview) (such as ACME, EST, API, etc.) used to enroll certificates.
|
|
|
|
- [Certificate Policy](/documentation/platform/pki/certificates/policies): A policy structure specifying the permitted attributes for requested certificates including subject naming conventions, SAN fields, key usages, and extended key usages.
|
|
|
|
- [Approval Policy](/documentation/platform/pki/approvals): An optional approval workflow requiring human review before certificates are issued. Approval policies can enforce multi-step review processes with configurable approvers for each step.
|
|
|
|
- [Certificate](/documentation/platform/pki/certificates/certificates): The actual X.509 certificate issued for a profile. Once issued, a certificate kept track of in the certificate inventory.
|