awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-09-22 13:39:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revise PR based on review

Browse Source
This commit is contained in:
Tuan Dang
2025-05-12 12:56:56 -07:00
parent 531607dcb7
commit e8519f6612
14 changed files with 100 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/documentation/platform/pki/subscribers.mdx
View File

@@ -12,10 +12,9 @@ In Infisical PKI, subscribers are logical representations of entities such as de
```mermaid
graph TD
A[Root CA] --> B[Intermediate CA]
B --> C1[Certificate]
A[Issuing CA] --> C1[Certificate]
C1 --> S1[Subscriber]
B --> C2[Certificate]
A --> C2[Certificate]
C2 --> S2[Subscriber]
```
@@ -25,7 +24,7 @@ graph TD
The typical workflow for managing subscribers consists of the following steps:
1. Creating a subscriber and defining attributes to be included on the X.509 certificates issued for it including common name, subject alternative names, TLL, etc.
1. Creating a subscriber and defining which (issuing) CA will issue X.509 certificates for it as well as attributes to be included on the certificates including common name, subject alternative names, TLL, etc.
2. Requesting for a certificate against the subscriber with or without a certificate signing request (CSR).
3. Managing certificate lifecycle events such as certificate renewal and revocation. As part of the certificate revocation flow,
you can also query for a Certificate Revocation List [CRL](https://en.wikipedia.org/wiki/Certificate_revocation_list), a time-stamped, signed