Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
TypeScript acmeagentsai-agentscertificate-managementdevsecopsenvironment-variableskubernetesopen-sourcepampkipostgresprivate-caprivileged-access-managementsecret-managementsecret-managersecretssecrets-managementsecuritysecurity-toolsvault
docs(pki): move issuance failure docs under certificate manager filters
bernie-g0e412973b1cc
diff --git a/docs/documentation/platform/audit-logs.mdx b/docs/documentation/platform/audit-logs.mdxindex 20a521d52f..6f56f5ea21 100644--- a/docs/documentation/platform/audit-logs.mdx+++ b/docs/documentation/platform/audit-logs.mdx@@ -303,28 +303,6 @@ Denials are only recorded for organizations on the new privilege system. If yourTo keep a misconfigured client from filling the log, Infisical records the first `permission-denied` event per actor, project, action, subject, and endpoint in each minute. Denials that repeat inside that minute are counted rather than recorded. When the minute ends, Infisical writes one more `permission-denied` event for the same combination with the count in `suppressedRepeats` and the minute in `suppressedFrom` and `suppressedUntil`. If nothing repeated, no summary event is written.-### Certificate issuance failures--If Infisical can't issue a certificate, it records a `certificate-issuance-failed` event with the reason. Infisical records the event for certificates requested from a certificate profile through the API or the Infisical UI, ACME, EST, and SCEP, including renewals and certificates issued after an approval. The event is in the `management` class, so it's always recorded.--If an automatic renewal fails before Infisical sends it to an external CA, Infisical records an `automated-renew-certificate-failed` event instead. Infisical doesn't record the event for EST enrollment through a certificate template, or for EST requests rejected before Infisical reads the CSR, such as a failed sign-in.--The event records which certificate failed and why:--- `operation`: what was requested (`issue`, `sign`, `order`, or `renew`)-- `enrollmentType`: how the certificate was requested (`api`, `acme`, `est`, or `scep`)-- `error` and `errorName`: why issuance failed, such as a TTL longer than the certificate policy allows or an error from the CA-- `certificateProfileId`, `profileName`, `caId`, `caName`, `commonName`, `applicationId`, and `applicationName`: the certificate the request was for, where Infisical knows them-- `certificateRequestId`: the certificate request that failed, if Infisical had already created one-- `originalCertificateId`: on a failed renewal, the certificate being renewed-- `suppressedRepeats`, `suppressedFrom`, and `suppressedUntil`: on a summary event, how many identical failures Infisical counted instead of recording, and the minute they fell in--If issuance fails in a background job, or after an approver approves the request, the event's actor is `platform`. A background job issues the certificate when the CA is external, such as DigiCert or AWS Private CA. To find who requested a certificate through the API or the Infisical UI, look for the request's original event, such as `order-certificate-from-profile`, with the same `certificateRequestId`.--If a request is denied because the actor's role doesn't allow it, Infisical records a [`permission-denied` event](#permission-denials) instead.--Infisical counts identical failures the same way it counts [repeated denials](#permission-denials). In each minute, it records the first failure with a given actor, operation, certificate, and error, then writes one summary event when the minute ends.-## Filtering audit logsYou can filter audit logs to find events more easily. When you set more than one filter, an event needs to match all of them to appear in the results.@@ -606,6 +584,51 @@ Here are a few common patterns for filtering audit logs, grouped by product.</Tab></Tabs></Accordion>+ <Accordion title="Why a certificate failed to issue" id="certificate-issuance-failures">+ Find every certificate that Infisical couldn't issue, and the reason for each failure.++ Infisical records a `certificate-issuance-failed` event for certificates requested from a certificate profile through the API or the Infisical UI, ACME, EST, and SCEP, including renewals and certificates issued after an approval. The event is in the `management` class, so it's always recorded.++ <Note>+ If an automatic renewal fails before Infisical sends it to an external CA, Infisical records an `automated-renew-certificate-failed` event instead. Infisical doesn't record `certificate-issuance-failed` for EST enrollment through a certificate template, for EST requests rejected before Infisical reads the CSR (such as a failed sign-in), or for requests the actor's role doesn't allow, which are recorded as [`permission-denied` events](#permission-denials).+ </Note>++ <Tabs>+ <Tab title="Infisical UI">+ <Steps>+ <Step>+ Go to **Certificate Manager**, select the project, and open **Audit Logs**.+ </Step>+ <Step>+ Select **Search audit logs** and add:+ - `event`: `certificate-issuance-failed`+ </Step>+ </Steps>+ </Tab>+ <Tab title="API">+ ```bash+ curl -G "https://app.infisical.com/api/v1/organization/audit-logs" \+ -H "Authorization: Bearer <your-access-token>" \+ --data-urlencode "projectId=<project-id>" \+ --data-urlencode "eventType=certificate-issuance-failed"+ ```+ </Tab>+ </Tabs>++ The `event.metadata` of each result records which certificate failed and why:++ - `operation`: what was requested (`issue`, `sign`, `order`, or `renew`)+ - `enrollmentType`: how the certificate was requested (`api`, `acme`, `est`, or `scep`)+ - `error` and `errorName`: why issuance failed, such as a TTL longer than the certificate policy allows or an error from the CA+ - `certificateProfileId`, `profileName`, `caId`, `caName`, `commonName`, `applicationId`, and `applicationName`: the certificate the request was for, where Infisical knows them+ - `certificateRequestId`: the certificate request that failed, if Infisical had already created one+ - `originalCertificateId`: on a failed renewal, the certificate being renewed+ - `suppressedRepeats`, `suppressedFrom`, and `suppressedUntil`: on a summary event, how many identical failures Infisical counted instead of recording, and the minute they fell in++ If issuance fails in a background job, or after an approver approves the request, the event's actor is `platform`. A background job issues the certificate when the CA is external, such as DigiCert or AWS Private CA. To find who requested a certificate through the API or the Infisical UI, filter by the original event, such as `order-certificate-from-profile`, and match the `certificateRequestId`.++ Infisical counts identical failures the same way it counts [repeated denials](#permission-denials). In each minute, it records the first failure with a given actor, operation, certificate, and error, then writes one summary event when the minute ends.+ </Accordion><Accordion title="Who revoked a certificate">Find every revocation in a project.diff --git a/docs/documentation/platform/pki/applications/approvals.mdx b/docs/documentation/platform/pki/applications/approvals.mdxindex ee8d6ad726..242e5ceebe 100644--- a/docs/documentation/platform/pki/applications/approvals.mdx+++ b/docs/documentation/platform/pki/applications/approvals.mdx@@ -100,7 +100,7 @@ In the Certificate Manager sidebar, go to **Approval Requests** to see all pendi</Step></Steps>-Once all required approvals are obtained, the certificate is automatically issued.+Once all required approvals are obtained, the certificate is automatically issued. If issuance fails at that point, for example because the CA is disabled, the certificate request moves to **Failed** and Infisical records a [`certificate-issuance-failed` audit log event](/documentation/platform/audit-logs#certificate-issuance-failures) with the reason.### Reject a requestdiff --git a/docs/documentation/platform/pki/applications/certificate-renewal.mdx b/docs/documentation/platform/pki/applications/certificate-renewal.mdxindex 8f28245b98..5fac237bd3 100644--- a/docs/documentation/platform/pki/applications/certificate-renewal.mdx+++ b/docs/documentation/platform/pki/applications/certificate-renewal.mdx@@ -174,6 +174,9 @@ Deploy the renewed certificate before the previous one expires. Renewing doesn't<Accordion title="Can I renew a certificate that Infisical did not generate the key for?">Yes. Choose a new key pair, or supply a CSR generated from the existing key. A certificate issued from a signing request can also reuse its public key, in which case the renewal is made from that original request.</Accordion>+ <Accordion title="Where can I see why a renewal failed?">+ If a manual renewal fails, Infisical shows the reason when you submit it and records a [`certificate-issuance-failed` audit log event](/documentation/platform/audit-logs#certificate-issuance-failures) that links to the certificate being renewed. If an automatic renewal fails, Infisical records an `automated-renew-certificate-failed` event instead, unless the renewal had already been sent to an external CA, in which case the failure is recorded as `certificate-issuance-failed`.+ </Accordion><Accordion title="Can I renew several certificates at once?">Manual renewal handles one certificate at a time. To keep many certificates current without intervention, enable [automatic renewal](/documentation/platform/pki/applications/certificates) so Infisical reissues them before they expire.</Accordion>diff --git a/docs/documentation/platform/pki/applications/certificates.mdx b/docs/documentation/platform/pki/applications/certificates.mdxindex c44d66a12f..1a6381c343 100644--- a/docs/documentation/platform/pki/applications/certificates.mdx+++ b/docs/documentation/platform/pki/applications/certificates.mdx@@ -54,6 +54,12 @@ For automated issuance, configure an [enrollment method](/documentation/platform- [EST](/documentation/platform/pki/applications/enrollment-methods/est) — RFC 7030 enrollment- [SCEP](/documentation/platform/pki/applications/enrollment-methods/scep) — Mobile device management (Jamf, Intune)+### When issuance fails++If Infisical creates a certificate request and then can't issue the certificate, the request shows a **Failed** status on the **Certificate Requests** tab. Hover over the status to see the reason.++Some requests are rejected before Infisical creates a certificate request, such as a request for a TTL longer than the certificate policy allows, so they don't appear on the tab. Infisical records every failure, including these, as a `certificate-issuance-failed` event in the [audit logs](/documentation/platform/audit-logs#certificate-issuance-failures), with the reason and the certificate the request was for.+## Importing certificatesSelect **Import** on the Certificates tab to bring in a certificate you already hold, either as PEM files or as a `.p12` / `.pfx` keystore with its password.