Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

Merge branch 'main' of https://github.com/Infisical/infisical into sheensantoscapadngan/sheen-pki-503-allow-pki-admins-to-configure-signer-specific-code-signing

Sheen Capadngan7b3ea1dbdc36
diff --cc docs/documentation/platform/pki/applications/alerting/overview.mdx
index ed5736870e,bc015ed388..6cd2f6484c
--- a/docs/documentation/platform/pki/applications/alerting/overview.mdx
+++ b/docs/documentation/platform/pki/applications/alerting/overview.mdx
@@@ -65,10 -65,6 +65,10 @@@ An expiration alert keeps notifying yo
## Signer certificate expiration
- A **Signer Certificate Expiration** alert, in the **Code Signing** group, warns you before a [signer's](/documentation/platform/pki/code-signing/signers) current certificate expires. You can only create it as a Certificate Manager alert. Otherwise, it works like a certificate expiration alert.
-A **Signer Certificate Expiration** alert, in the **Code Signing** group, warns you before a [signer's](/documentation/platform/pki/code-signing/signers) current certificate expires. You can only create it as a Certificate Management alert. It covers every active signer under **Code Signing** > **Signers** and skips the **Filters** step. Otherwise, it works like a certificate expiration alert.
++A **Signer Certificate Expiration** alert, in the **Code Signing** group, warns you before a [signer's](/documentation/platform/pki/code-signing/signers) current certificate expires. You can only create it as a Certificate Management alert. Otherwise, it works like a certificate expiration alert.
+
+Without filters, the alert covers every active signer under **Code Signing** > **Signers**. To cover only some signers, add a **Signers** filter in the **Filters** step and select up to 100 signers. If several signers share a certificate, the notification names only the selected ones.
+
+If you delete a signer that the filter lists, the deleted signer stays in the filter and matches no certificates. When you edit the alert, the **Filters** step shows it as **Unknown signer**, so you can remove it.
When you reissue a signer's certificate, the alert follows the new certificate and stops alerting on the one it replaced. The alert doesn't cover disabled, failed, or pending signers.
diff --cc docs/documentation/platform/pki/applications/alerting/webhook-alerts.mdx
index 7b98d9b21f,904bf4ebf9..5c506405a4
--- a/docs/documentation/platform/pki/applications/alerting/webhook-alerts.mdx
+++ b/docs/documentation/platform/pki/applications/alerting/webhook-alerts.mdx
@@@ -91,8 -91,8 +91,8 @@@ The `subject` field is the same value w
To find out which kind of alert sent a request, read `data.alert.resourceType`:
- `cert-manager.application`: an application alert, with the application's ID in `data.alert.resourceId`
- - `cert-manager`: a Certificate Manager alert
+ - `cert-manager`: a Certificate Management alert
-- `cert-manager.signer`: a signer certificate expiration alert, whose items list the signers in `resource.signerIds` and `resource.signerNames`
+- `cert-manager.signer`: a signer certificate expiration alert, whose items list the signers in `resource.signerIds` and `resource.signerNames`. If the alert has a **Signers** filter, the items list only the selected signers.
<Note>
Alerts created before certificate alerts moved to applications keep sending the older `com.infisical.pki.certificate.*` event types with a `data.certificates` list. If one endpoint receives both, check the `type` field to tell them apart.