feature: add PKI approval workflows#5218
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Greptile SummaryThis PR implements approval workflows for PKI certificate issuance, allowing administrators to require approval before certificates are issued from specific profiles. The implementation includes backend approval policy matching, multi-step approval flows, and frontend UI for managing policies and approving requests. Key Changes:
Critical Issues Found:
Confidence Score: 2/5
Important Files Changed
|
There was a problem hiding this comment.
Additional Comments (1)
-
backend/src/server/routes/v1/certificate-router.ts, line 175-192 (link)logic: Breaking API Change: response schema now includes optional
statusandmessagefields, andcertificatecan be null when status isPENDING_APPROVAL. Existing API consumers expecting certificates to always be returned will break.Consider versioning this endpoint (e.g.,
/v2/certificates/issue) or ensuring backwards compatibility by always including certificate data in v1.
73 files reviewed, 7 comments
Context
This PR adds approval workflows for certificate issuance. When users request certificates, the backend checks for approval policies on the certificate profile and, if required, creates an approval request that must be approved before the certificate is issued. Admins can create approval policies that specify which profiles require approval, how many approvers are needed, and who can approve. The frontend includes pages to view pending approval requests, approve or reject them, and manage approval policies. Certificate requests are linked to approval requests, and the certificate is only issued after the approval workflow completes.
Screenshots
Steps to verify the change
Type
Checklist
type(scope): short description(scope is optional, e.g.,fix: prevent crash on syncorfix(api): handle null response).