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): update cert management ia and content (#8622)
Adrian Kahali26e955114bf5
diff --git a/docs/docs.json b/docs/docs.jsonindex 3eb1c43bc2..9e74f05d63 100644--- a/docs/docs.json+++ b/docs/docs.json@@ -420,17 +420,12 @@"icon": "file-key","pages": ["documentation/platform/pki/overview",+ "documentation/platform/pki/migration",{- "group": "Certificate management",+ "group": "Get started","pages": [- {- "group": "Quickstarts",- "pages": [- "documentation/platform/pki/getting-started",- "documentation/platform/pki/quick-starts/issue-first-certificate",- "documentation/platform/pki/quick-starts/sign-first-code"- ]- },+ "documentation/platform/pki/quick-starts/issue-first-certificate",+ "documentation/platform/pki/quick-starts/sign-first-code",{"group": "Concepts","pages": [@@ -439,169 +434,168 @@"documentation/platform/pki/concepts/access-control","documentation/platform/pki/concepts/reference-architecture"]+ }+ ]+ },+ {+ "group": "Certificate authorities",+ "pages": [+ "documentation/platform/pki/ca/overview",+ {+ "group": "Internal CA",+ "root": "documentation/platform/pki/ca/private-ca",+ "pages": [+ "documentation/platform/pki/ca/ca-renewal",+ "documentation/platform/pki/ca/crl-distribution",+ "documentation/platform/pki/ca/ocsp",+ "documentation/platform/pki/reference/pqc-algorithms"+ ]},{- "group": "Guides",+ "group": "External CA",+ "root": "documentation/platform/pki/ca/external-ca","pages": [- "documentation/platform/pki/guides/overview",- {- "group": "Applications",- "pages": [- "documentation/platform/pki/guides/applications/infisical-agent",- "documentation/platform/pki/guides/applications/k8s-cert-manager-acme",- "documentation/platform/pki/guides/applications/k8s-cert-manager-issuer",- "documentation/platform/pki/guides/applications/nginx-certbot",- "documentation/platform/pki/guides/applications/apache-certbot",- "documentation/platform/pki/guides/applications/tomcat-certbot",- "documentation/platform/pki/guides/applications/jboss-certbot",- "documentation/platform/pki/guides/applications/windows-server-acme",- "documentation/platform/pki/guides/applications/gloo-mesh",- "documentation/platform/pki/guides/applications/jamf-pro-scep",- "documentation/platform/pki/guides/applications/microsoft-intune-scep"- ]- },- {- "group": "Code signing",- "pages": [- "documentation/platform/pki/guides/code-signing/digicert-code-signing",- "documentation/platform/pki/guides/code-signing/jarsigner",- "documentation/platform/pki/guides/code-signing/apksigner",- "documentation/platform/pki/guides/code-signing/osslsigncode",- "documentation/platform/pki/guides/code-signing/cosign",- "documentation/platform/pki/guides/code-signing/openssl",- "documentation/platform/pki/guides/code-signing/gpg"- ]- }+ "documentation/platform/pki/ca/acme-ca",+ "documentation/platform/pki/ca/lets-encrypt",+ "documentation/platform/pki/ca/digicert",+ "documentation/platform/pki/ca/digicert-direct",+ "documentation/platform/pki/ca/godaddy",+ "documentation/platform/pki/ca/sectigo",+ "documentation/platform/pki/ca/adcs",+ "documentation/platform/pki/ca/azure-adcs",+ "documentation/platform/pki/ca/aws-pca",+ "documentation/platform/pki/ca/aws-acm-public-ca",+ "documentation/platform/pki/ca/venafi",+ "documentation/platform/pki/ca/venafi-tpp"+ ]+ },+ {+ "group": "HSM connectors",+ "root": "documentation/platform/pki/settings/hsm-connectors",+ "pages": [+ "documentation/platform/pki/settings/hsm-connectors-fortanix-dsm"]}]},{- "group": "Product reference",+ "group": "Managing certificates","pages": [+ "documentation/platform/pki/applications/overview",+ "documentation/platform/pki/settings/policies",+ "documentation/platform/pki/settings/profiles",{- "group": "Applications",+ "group": "Enrollment methods",+ "root": "documentation/platform/pki/applications/enrollment-methods/overview","pages": [- "documentation/platform/pki/applications/overview",- "documentation/platform/pki/applications/certificates",- "documentation/platform/pki/applications/certificate-renewal",{- "group": "Enrollment methods",+ "group": "API",+ "root": "documentation/platform/pki/applications/enrollment-methods/api","pages": [- "documentation/platform/pki/applications/enrollment-methods/overview",- "documentation/platform/pki/applications/enrollment-methods/api",- "documentation/platform/pki/applications/enrollment-methods/acme",- "documentation/platform/pki/applications/enrollment-methods/est",- "documentation/platform/pki/applications/enrollment-methods/scep"+ "documentation/platform/pki/guides/applications/infisical-agent",+ "documentation/platform/pki/reference/infisical-agent",+ "documentation/platform/pki/guides/applications/k8s-cert-manager-issuer"]},- "documentation/platform/pki/applications/approvals",{- "group": "Alerting",+ "group": "ACME",+ "root": "documentation/platform/pki/applications/enrollment-methods/acme","pages": [- "documentation/platform/pki/applications/alerting/overview",- "documentation/platform/pki/applications/alerting/webhook-alerts",- "documentation/platform/pki/applications/alerting/slack-alerts",- "documentation/platform/pki/applications/alerting/pagerduty-alerts"+ "documentation/platform/pki/guides/applications/k8s-cert-manager-acme",+ "documentation/platform/pki/guides/applications/nginx-certbot",+ "documentation/platform/pki/guides/applications/apache-certbot",+ "documentation/platform/pki/guides/applications/tomcat-certbot",+ "documentation/platform/pki/guides/applications/jboss-certbot",+ "documentation/platform/pki/guides/applications/windows-server-acme",+ "documentation/platform/pki/guides/applications/gloo-mesh"]},+ "documentation/platform/pki/applications/enrollment-methods/est",{- "group": "Certificate syncs",+ "group": "SCEP",+ "root": "documentation/platform/pki/applications/enrollment-methods/scep","pages": [- "documentation/platform/pki/applications/certificate-syncs/overview",- "documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager",- "documentation/platform/pki/applications/certificate-syncs/aws-elastic-load-balancer",- "documentation/platform/pki/applications/certificate-syncs/aws-secrets-manager",- "documentation/platform/pki/applications/certificate-syncs/azure-key-vault",- "documentation/platform/pki/applications/certificate-syncs/chef",- "documentation/platform/pki/applications/certificate-syncs/cloudflare-custom-certificate",- "documentation/platform/pki/applications/certificate-syncs/f5-big-ip",- "documentation/platform/pki/applications/certificate-syncs/netscaler",- "documentation/platform/pki/applications/certificate-syncs/palo-alto-networks",- "documentation/platform/pki/applications/certificate-syncs/palo-alto-networks-ssl-tls-profile",- "documentation/platform/pki/applications/certificate-syncs/kemp-loadmaster",- "documentation/platform/pki/applications/certificate-syncs/linux-server",- "documentation/platform/pki/applications/certificate-syncs/windows-server",- "documentation/platform/pki/applications/certificate-syncs/nutanix-prism-central",- "documentation/platform/pki/applications/certificate-syncs/gcp-certificate-manager"+ "documentation/platform/pki/guides/applications/jamf-pro-scep",+ "documentation/platform/pki/guides/applications/microsoft-intune-scep"]}]},+ "documentation/platform/pki/applications/certificates",+ "documentation/platform/pki/applications/approvals",+ "documentation/platform/pki/applications/certificate-renewal",{- "group": "Code signing",+ "group": "Certificate syncs",+ "root": "documentation/platform/pki/applications/certificate-syncs/overview","pages": [- "documentation/platform/pki/code-signing/overview",- "documentation/platform/pki/code-signing/signers",- "documentation/platform/pki/code-signing/approvals",- "documentation/platform/pki/code-signing/pkcs11-module",- "documentation/platform/pki/code-signing/windows-ksp"+ "documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager",+ "documentation/platform/pki/applications/certificate-syncs/aws-elastic-load-balancer",+ "documentation/platform/pki/applications/certificate-syncs/aws-secrets-manager",+ "documentation/platform/pki/applications/certificate-syncs/azure-key-vault",+ "documentation/platform/pki/applications/certificate-syncs/chef",+ "documentation/platform/pki/applications/certificate-syncs/cloudflare-custom-certificate",+ "documentation/platform/pki/applications/certificate-syncs/f5-big-ip",+ "documentation/platform/pki/applications/certificate-syncs/netscaler",+ "documentation/platform/pki/applications/certificate-syncs/palo-alto-networks",+ "documentation/platform/pki/applications/certificate-syncs/palo-alto-networks-ssl-tls-profile",+ "documentation/platform/pki/applications/certificate-syncs/kemp-loadmaster",+ "documentation/platform/pki/applications/certificate-syncs/linux-server",+ "documentation/platform/pki/applications/certificate-syncs/windows-server",+ "documentation/platform/pki/applications/certificate-syncs/nutanix-prism-central",+ "documentation/platform/pki/applications/certificate-syncs/gcp-certificate-manager"]- },+ }+ ]+ },+ {+ "group": "Monitoring",+ "pages": [+ "documentation/platform/pki/monitoring/certificate-inventory",{- "group": "Certificate discovery",+ "group": "Discovery",+ "root": "documentation/platform/pki/discovery/overview","pages": [- "documentation/platform/pki/discovery/overview","documentation/platform/pki/discovery/network"]},{- "group": "Certificate authorities",+ "group": "Alerts",+ "root": "documentation/platform/pki/applications/alerting/overview","pages": [- "documentation/platform/pki/ca/overview",- {- "group": "Internal CA",- "pages": [- "documentation/platform/pki/ca/private-ca",- "documentation/platform/pki/ca/ca-renewal",- "documentation/platform/pki/ca/crl-distribution",- "documentation/platform/pki/ca/ocsp"- ]- },- {- "group": "External CA",- "pages": [- "documentation/platform/pki/ca/external-ca",- "documentation/platform/pki/ca/acme-ca",- "documentation/platform/pki/ca/lets-encrypt",- "documentation/platform/pki/ca/digicert",- "documentation/platform/pki/ca/digicert-direct",- "documentation/platform/pki/ca/godaddy",- "documentation/platform/pki/ca/sectigo",- "documentation/platform/pki/ca/adcs",- "documentation/platform/pki/ca/azure-adcs",- "documentation/platform/pki/ca/aws-pca",- "documentation/platform/pki/ca/aws-acm-public-ca",- "documentation/platform/pki/ca/venafi",- "documentation/platform/pki/ca/venafi-tpp"- ]- }+ "documentation/platform/pki/applications/alerting/email-alerts",+ "documentation/platform/pki/applications/alerting/slack-alerts",+ "documentation/platform/pki/applications/alerting/pagerduty-alerts",+ "documentation/platform/pki/applications/alerting/webhook-alerts"]},- {- "group": "Settings",- "pages": [- "documentation/platform/pki/settings/policies",- "documentation/platform/pki/settings/profiles",- "documentation/platform/pki/settings/certificate-cleanup",- "documentation/platform/pki/settings/alerts",- {- "group": "HSM",- "pages": [- "documentation/platform/pki/settings/hsm-connectors",- "documentation/platform/pki/settings/hsm-connectors-fortanix-dsm"- ]- }- ]- }+ "documentation/platform/pki/settings/certificate-cleanup"]},{- "group": "Reference",+ "group": "Code signing","pages": [- "documentation/platform/pki/reference/pqc-algorithms",- "documentation/platform/pki/reference/infisical-agent",- "documentation/platform/pki/migration"+ "documentation/platform/pki/code-signing/overview",+ {+ "group": "Signers",+ "root": "documentation/platform/pki/code-signing/signers",+ "pages": [+ "documentation/platform/pki/guides/code-signing/digicert-code-signing"+ ]+ },+ "documentation/platform/pki/code-signing/approvals",+ {+ "group": "Signing tools",+ "pages": [+ "documentation/platform/pki/guides/code-signing/jarsigner",+ "documentation/platform/pki/guides/code-signing/apksigner",+ "documentation/platform/pki/guides/code-signing/osslsigncode",+ "documentation/platform/pki/guides/code-signing/cosign",+ "documentation/platform/pki/guides/code-signing/openssl",+ "documentation/platform/pki/guides/code-signing/gpg"+ ]+ },+ "documentation/platform/pki/code-signing/pkcs11-module",+ "documentation/platform/pki/code-signing/windows-ksp"]}]@@ -5480,6 +5474,18 @@"source": "/documentation/platform/pki/enrollment-methods/scep","destination": "/documentation/platform/pki/applications/enrollment-methods/scep"},+ {+ "source": "/documentation/platform/pki/getting-started",+ "destination": "/documentation/platform/pki/overview"+ },+ {+ "source": "/documentation/platform/pki/guides/overview",+ "destination": "/documentation/platform/pki/applications/enrollment-methods/overview"+ },+ {+ "source": "/documentation/platform/pki/settings/alerts",+ "destination": "/documentation/platform/pki/applications/alerting/overview"+ },{"source": "/documentation/platform/oauth-applications","destination": "/documentation/platform/oauth-applications/overview"diff --git a/docs/documentation/platform/pki/applications/alerting/email-alerts.mdx b/docs/documentation/platform/pki/applications/alerting/email-alerts.mdxnew file mode 100644index 0000000000..e74df08afc--- /dev/null+++ b/docs/documentation/platform/pki/applications/alerting/email-alerts.mdx@@ -0,0 +1,45 @@+---+title: "Email alerts"+sidebarTitle: "Email"+description: "Send certificate alert notifications by email."+---++import StartAlert from "/snippets/documentation/platform/pki/applications/alerting/start-alert.mdx";++An email channel on a certificate [alert](/documentation/platform/pki/applications/alerting/overview) emails the recipients you choose whenever the alert fires. Email channels are available on every plan.++<Note>+ If you self-host Infisical, [configure an SMTP server](/self-hosting/configuration/envars#email-service) before you create an email alert. Without one, Infisical writes alert emails to its logs instead of sending them, so a **Send test** can look successful even though no email arrives.+</Note>++## Prerequisites++- The Certificate Manager **Admin** role to create a Certificate Manager alert, or the **Admin** [application role](/documentation/platform/pki/applications/overview#application-roles) to create an application alert+- Recipients who are organization members, or addresses on one of your organization's [verified email domains](/documentation/platform/email-domain)++## Step 1: Start an alert++<StartAlert />++## Step 2: Add the email channel++<Steps>+ <Step>+ Select **Add Channel** > **Email**.+ </Step>+ <Step>+ In **Recipients**, select organization members, or type an address on one of your organization's verified email domains and add it.+ </Step>+ <Step>+ Optionally, select **Send test** to send a test email to the recipients.+ </Step>+ <Step>+ Select **Continue**, check the **Review** step, and select **Create Alert**.+ </Step>+</Steps>++<Check>+ Your alert is set up. Infisical emails the recipients whenever the alert fires.+</Check>++If a recipient is an organization member, they stop receiving alerts when they leave the organization.diff --git a/docs/documentation/platform/pki/applications/alerting/overview.mdx b/docs/documentation/platform/pki/applications/alerting/overview.mdxindex 2378f83b79..a5df046e44 100644--- a/docs/documentation/platform/pki/applications/alerting/overview.mdx+++ b/docs/documentation/platform/pki/applications/alerting/overview.mdx@@ -1,104 +1,69 @@----title: "Alerting"-sidebarTitle: "Overview"-description: "Get notified when certificates in an application expire, are issued, renewed, or revoked."+title: "Alerts"+description: "Get notified when certificates expire, are issued, renewed, or revoked, across Certificate Manager or in one application."----Certificate alerting tells your team about certificate lifecycle events in an [Application](/documentation/platform/pki/applications/overview). You create alerts in the application, and each alert covers every certificate in the application for one event. To alert on certificates across Certificate Manager, including ones outside an application, create an alert under [**Settings** > **Alerts**](/documentation/platform/pki/settings/alerts).--## Alert events+An alert notifies your team when a certificate is about to expire, or when a certificate is issued, renewed, or revoked. Each alert watches for one of these events and sends a notification to up to 10 channels. To create an alert, follow the guide for the channel you want to notify:<CardGroup cols={2}>- <Card title="Expiration" icon="clock">- Notifies a set number of days before a certificate expires.- </Card>- <Card title="Issuance" icon="award">- Notifies immediately when a new certificate is issued.- </Card>- <Card title="Renewal" icon="rotate-cw">- Notifies when a certificate is renewed.- </Card>- <Card title="Revocation" icon="ban">- Notifies when a certificate is revoked.+ <Card title="Email" icon="mail" href="/documentation/platform/pki/applications/alerting/email-alerts">+ Email organization members or addresses on your verified domains.</Card>-</CardGroup>--Expiration alerts are checked once a day. Issuance, renewal, and revocation alerts are sent within seconds of the event. Importing a certificate into the application doesn't trigger an Issuance alert, but expiration and revocation alerts still cover imported certificates.--## Prerequisites--- For email alerts, recipients who are organization members, or addresses on one of your organization's [verified email domains](/documentation/platform/email-domain)--## Create an alert--<Steps>- <Step>- Go to **Certificate Manager** > **Applications** and select your application.- </Step>- <Step>- Select the **Settings** tab, then select **Create Alert** in the **Alerts** section.- </Step>- <Step>- Choose the **Alert Type**, then enter an **Alert Name** and an optional **Description**.- </Step>- <Step>- For an expiration alert, enter **Alert Before** as a number and a unit, for example `30d` or `2w`, up to 365 days. Turn on **Repeat daily until expiry** to get a reminder every day. See [how often expiration alerts repeat](#faq). Select **Continue**.- </Step>- <Step>- Select **Add Channel** and choose where to send notifications. You can add up to 10 channels. See [Notification channels](#notification-channels). To check a channel, select **Send test** on it. Select **Continue**.- </Step>- <Step>- Check the summary on the **Review** step, then select **Create Alert**.- </Step>-</Steps>--An application can have one alert of each type. To notify more places about the same event, add more channels to that alert.--## Notification channels--| Channel | Sends to |-|---------|----------|-| **Email** | Organization members, or any address on one of your organization's verified email domains |-| **[Slack](/documentation/platform/pki/applications/alerting/slack-alerts)** | A Slack channel through an Incoming Webhook |-| **[PagerDuty](/documentation/platform/pki/applications/alerting/pagerduty-alerts)** | A PagerDuty service through Events API v2 |-| **[Webhook](/documentation/platform/pki/applications/alerting/webhook-alerts)** | Any HTTPS endpoint, with an optional signature |--## FAQ--<AccordionGroup>- <Accordion title="Who receives email alerts?">- The addresses you enter on the email channel. An address that belongs to an organization member only receives alerts while that person is still in the organization. Any other address has to be on one of your organization's [verified email domains](/documentation/platform/email-domain) when you add it.- </Accordion>- <Accordion title="How often does an expiration alert notify about the same certificate?">- The alert repeats until the certificate is renewed or expires. How often it repeats depends on the alert's **Alert Before** setting:-- | Alert before | Repeats every |- |--------------|---------------|- | 7 days or fewer | Day |- | 8 to 30 days | 2 days |- | 31 to 90 days | 7 days |- | More than 90 days | 30 days |-- If you turn on **Repeat daily until expiry**, the alert repeats every day.- </Accordion>- <Accordion title="What happens to an alert when I delete its application?">- The application's alerts and their channels are deleted along with the application.- </Accordion>-</AccordionGroup>--## What's next?--<CardGroup cols={2}><Card title="Slack" icon="slack" iconType="brands" href="/documentation/platform/pki/applications/alerting/slack-alerts">- Set up a Slack Incoming Webhook.+ Post to a Slack channel through an incoming webhook.</Card><Card title="PagerDuty" icon="radio-tower" href="/documentation/platform/pki/applications/alerting/pagerduty-alerts">- Create incidents with the PagerDuty Events API.+ Open PagerDuty incidents through the Events API.</Card><Card title="Webhook" icon="webhook" href="/documentation/platform/pki/applications/alerting/webhook-alerts">- Send alerts to your own endpoint.- </Card>- <Card title="Certificates" icon="award" href="/documentation/platform/pki/applications/certificates">- View and manage your certificate inventory.+ Send a request to your own HTTPS endpoint, optionally signed.</Card></CardGroup>++Infisical checks for expiring certificates once a day, and sends issuance, renewal, and revocation alerts within seconds of the event. Importing a certificate into an application doesn't trigger an issuance alert, but the application's other alerts still cover the imported certificate.++## Choose where to create an alert++You can create an alert for all of Certificate Manager or for one [application](/documentation/platform/pki/applications/overview):++| | Certificate Manager alert | Application alert |+| --- | --- | --- |+| Covers | Every certificate in Certificate Manager, or the ones that match its [filters](#filter-a-certificate-manager-alert) | Every certificate in the application |+| Created in | **Certificate Manager** > **Settings** > **Alerts** | The application's **Settings** tab |+| Who can create it | The Certificate Manager **Admin** role | The **Admin** [application role](/documentation/platform/pki/applications/overview#application-roles) |+| Events | Certificate events, plus [signer certificate expiration](#signer-certificate-expiration) for code signing | Certificate events, with one alert for each event |++Use an application alert when one team owns the certificates and wants its own notifications. Use a Certificate Manager alert to cover several applications at once, or certificates that don't belong to an application, such as imported or discovered certificates.++If you delete an application, Infisical deletes its alerts too.++## Filter a Certificate Manager alert++Without filters, a Certificate Manager alert covers every certificate in Certificate Manager. Each filter you add narrows the alert, and a certificate must match every filter:++| Filter | Certificates covered |+|--------|----------------------|+| **Applications** | Certificates in one of the selected applications (up to 100) |+| **Certificate Profiles** | Certificates issued from one of the selected profiles (up to 100) |+| **Source** | Certificates with one of the selected sources: **Managed** for certificates issued through Certificate Manager, **Imported**, or **Discovered** |++For example, a **Source** filter set to **Imported** covers every imported certificate, including ones outside any application or profile. Add an **Applications** filter as well, and the alert covers only the imported certificates in those applications.++If you delete an application or profile that a filter lists, the deleted application or profile stays in the filter and matches no certificates. When you edit the alert, the **Filters** step shows it as **Unknown application** or **Unknown profile**, so you can remove it.++## How often expiration alerts repeat++An expiration alert keeps notifying you about the same certificate until the certificate is renewed or expires. If you turn on **Repeat daily until expiry**, it notifies you every day. Otherwise, the interval depends on **Alert Before**:++| Alert before | Repeats every |+|--------------|---------------|+| 7 days or fewer | Day |+| 8 to 30 days | 2 days |+| 31 to 90 days | 7 days |+| More than 90 days | 30 days |++## 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. It covers every active signer under **Code Signing** > **Signers** and skips the **Filters** step. Otherwise, it works like a certificate expiration alert.++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 --git a/docs/documentation/platform/pki/applications/alerting/pagerduty-alerts.mdx b/docs/documentation/platform/pki/applications/alerting/pagerduty-alerts.mdxindex afe15fa4a8..ffcaca6ba2 100644--- a/docs/documentation/platform/pki/applications/alerting/pagerduty-alerts.mdx+++ b/docs/documentation/platform/pki/applications/alerting/pagerduty-alerts.mdx@@ -4,8 +4,19 @@ sidebarTitle: "PagerDuty"description: "Create PagerDuty incidents for certificate alerts."---+import StartAlert from "/snippets/documentation/platform/pki/applications/alerting/start-alert.mdx";+A PagerDuty channel on a certificate [alert](/documentation/platform/pki/applications/alerting/overview) creates PagerDuty incidents through the [Events API v2](https://developer.pagerduty.com/docs/events-api-v2-overview), so your on-call team gets paged when certificates are about to expire or are revoked.+<Info>+ PagerDuty channels are available under Infisical's [Enterprise](https://infisical.com/pricing) plan. If you're self-hosting Infisical, contact [email protected] to purchase an enterprise license.+</Info>++## Prerequisites++- The Certificate Manager **Admin** role to create a Certificate Manager alert, or the **Admin** [application role](/documentation/platform/pki/applications/overview#application-roles) to create an application alert+- A PagerDuty account that can create services or add integrations to an existing service+## Step 1: Get a PagerDuty integration key<Steps>@@ -28,23 +39,28 @@ A PagerDuty channel on a certificate [alert](/documentation/platform/pki/applica</Step></Steps>-## Step 2: Add the PagerDuty channel to an alert+## Step 2: Start an alert++<StartAlert />++## Step 3: Add the PagerDuty channel<Steps><Step>- [Create an alert](/documentation/platform/pki/applications/alerting/overview#create-an-alert) in your application, or edit an existing one.- </Step>- <Step>- Select **Add Channel** > **PagerDuty** and paste the integration key.+ Select **Add Channel** > **PagerDuty** and paste the key from [step 1](#step-1-get-a-pagerduty-integration-key) into **Integration key**.</Step><Step>- Optionally, select **Send test** to send a test notification to the channel.+ Optionally, select **Send test** to send a test event to the PagerDuty service.</Step><Step>Select **Continue**, check the **Review** step, and select **Create Alert**.</Step></Steps>+<Check>+ Your alert is set up. Infisical opens a PagerDuty incident whenever the alert fires.+</Check>+## Severity mappingEach incident's PagerDuty severity comes from the alert's event. For expiration alerts, it comes from how close the certificate is to expiry.@@ -71,20 +87,3 @@ Each incident's PagerDuty severity comes from the alert's event. For expirationEach certificate gets its own incident. If the same alert fires again for the same certificate, PagerDuty updates the existing incident instead of opening a new one.Each PagerDuty channel opens at most 10 incidents per run. If more than 10 certificates are due for an expiration alert, the ones closest to expiry go first and the rest go on the next daily run.--## What's next?--<CardGroup cols={2}>- <Card title="Webhook" icon="webhook" href="/documentation/platform/pki/applications/alerting/webhook-alerts">- Send alerts to your own endpoint.- </Card>- <Card title="Slack" icon="slack" iconType="brands" href="/documentation/platform/pki/applications/alerting/slack-alerts">- Send alerts to a Slack channel.- </Card>- <Card title="Certificate syncs" icon="refresh-cw" href="/documentation/platform/pki/applications/certificate-syncs/overview">- Push certificates to cloud destinations.- </Card>- <Card title="Certificates" icon="list" href="/documentation/platform/pki/applications/certificates">- View and manage certificates.- </Card>-</CardGroup>diff --git a/docs/documentation/platform/pki/applications/alerting/slack-alerts.mdx b/docs/documentation/platform/pki/applications/alerting/slack-alerts.mdxindex 18844f0edb..06b8cf65c9 100644--- a/docs/documentation/platform/pki/applications/alerting/slack-alerts.mdx+++ b/docs/documentation/platform/pki/applications/alerting/slack-alerts.mdx@@ -4,8 +4,19 @@ sidebarTitle: "Slack"description: "Send certificate alert notifications to a Slack channel."---+import StartAlert from "/snippets/documentation/platform/pki/applications/alerting/start-alert.mdx";+A Slack channel on a certificate [alert](/documentation/platform/pki/applications/alerting/overview) posts to a Slack channel through an [Incoming Webhook](https://api.slack.com/messaging/webhooks) whenever the alert fires.+<Info>+ Slack channels are available under Infisical's [Enterprise](https://infisical.com/pricing) plan. If you're self-hosting Infisical, contact [email protected] to purchase an enterprise license.+</Info>++## Prerequisites++- The Certificate Manager **Admin** role to create a Certificate Manager alert, or the **Admin** [application role](/documentation/platform/pki/applications/overview#application-roles) to create an application alert+- A Slack workspace where you can create apps+## Step 1: Create a Slack incoming webhook<Steps>@@ -30,46 +41,34 @@ A Slack channel on a certificate [alert](/documentation/platform/pki/application</Step></Steps>-## Step 2: Add the Slack channel to an alert+## Step 2: Start an alert++<StartAlert />++## Step 3: Add the Slack channel<Steps><Step>- [Create an alert](/documentation/platform/pki/applications/alerting/overview#create-an-alert) in your application, or edit an existing one.- </Step>- <Step>- Select **Add Channel** > **Slack** and paste the webhook URL. The URL must start with `https://hooks.slack.com`.+ Select **Add Channel** > **Slack** and paste the URL from [step 1](#step-1-create-a-slack-incoming-webhook) into **Webhook URL**. The URL must start with `https://hooks.slack.com`.</Step><Step>- Optionally, select **Send test** to send a test notification to the channel.+ Optionally, select **Send test** to send a test message to the Slack channel.</Step><Step>Select **Continue**, check the **Review** step, and select **Create Alert**.</Step></Steps>+<Check>+ Your alert is set up. Infisical posts to the Slack channel whenever the alert fires.+</Check>+## Message format-Each Slack message includes the alert's summary, up to two certificates, and a link to the application in Infisical. The message color shows the alert's severity:+Each Slack message includes the alert's summary, up to two certificates, and a **View in Infisical** button. For an application alert, the button opens the application. For a Certificate Manager alert, it opens the **Inventory** page, or the **Signers** page for a signer certificate expiration alert. The message color shows the alert's severity:| Color | Severity | When ||-------|----------|------|| Red | Critical or error | A certificate expires within 14 days || Amber | Warning | A certificate expires within 15 to 30 days, or a certificate was revoked || Blue | Info | A certificate expires in more than 30 days, or a certificate was issued or renewed |--## What's next?--<CardGroup cols={2}>- <Card title="Webhook" icon="webhook" href="/documentation/platform/pki/applications/alerting/webhook-alerts">- Send alerts to your own endpoint.- </Card>- <Card title="PagerDuty" icon="radio-tower" href="/documentation/platform/pki/applications/alerting/pagerduty-alerts">- Create incidents in PagerDuty.- </Card>- <Card title="Certificate syncs" icon="refresh-cw" href="/documentation/platform/pki/applications/certificate-syncs/overview">- Push certificates to cloud destinations.- </Card>- <Card title="Certificates" icon="list" href="/documentation/platform/pki/applications/certificates">- View and manage certificates.- </Card>-</CardGroup>diff --git a/docs/documentation/platform/pki/applications/alerting/webhook-alerts.mdx b/docs/documentation/platform/pki/applications/alerting/webhook-alerts.mdxindex a20cd8a10d..b73bdb4413 100644--- a/docs/documentation/platform/pki/applications/alerting/webhook-alerts.mdx+++ b/docs/documentation/platform/pki/applications/alerting/webhook-alerts.mdx@@ -4,50 +4,75 @@ sidebarTitle: "Webhook"description: "Send certificate alert notifications to a webhook URL."---+import StartAlert from "/snippets/documentation/platform/pki/applications/alerting/start-alert.mdx";+A webhook channel on a certificate [alert](/documentation/platform/pki/applications/alerting/overview) sends an HTTP POST request to your endpoint whenever the alert fires. Use a webhook to connect certificate alerts to your own systems or to services Infisical doesn't support directly.-## Add a webhook channel to an alert+<Info>+ Webhook channels are available under Infisical's [Enterprise](https://infisical.com/pricing) plan. If you're self-hosting Infisical, contact [email protected] to purchase an enterprise license.+</Info>++## Prerequisites++- The Certificate Manager **Admin** role to create a Certificate Manager alert, or the **Admin** [application role](/documentation/platform/pki/applications/overview#application-roles) to create an application alert+- An HTTPS endpoint that accepts POST requests++## Step 1: Start an alert++<StartAlert />++## Step 2: Add the webhook channel<Steps><Step>- [Create an alert](/documentation/platform/pki/applications/alerting/overview#create-an-alert) in your application, or edit an existing one.- </Step>- <Step>- Select **Add Channel** > **Webhook** and enter the **URL** of your endpoint. The URL must use HTTPS.+ Select **Add Channel** > **Webhook** and enter your endpoint's **URL**. The URL must use HTTPS.</Step><Step>- Optionally, enter a **Signing Secret** so your endpoint can [verify the signature](#verify-the-signature) of each request.+ Optionally, enter a **Signing secret** so your endpoint can [verify the signature](#verify-the-signature) of each request.</Step><Step>- Optionally, select **Send test** to send a test notification to the channel.+ Optionally, select **Send test** to send a test request to your endpoint.</Step><Step>Select **Continue**, check the **Review** step, and select **Create Alert**.</Step></Steps>+<Check>+ Your alert is set up. Infisical sends a POST request to your endpoint whenever the alert fires.+</Check>+## Webhook event types-Each request is a [CloudEvents](https://cloudevents.io/) JSON payload. The `type` and `subject` fields name the event:+Each request is a [CloudEvents](https://cloudevents.io/) JSON payload. The `type` field names the event, and application alerts and Certificate Manager alerts use different values:-| Event | `type` | `subject` |-|-------|--------|-----------|-| Expiration | `com.infisical.cert-manager.application.certificate.expiry` | `cert-manager.application.certificate.expiry` |-| Issuance | `com.infisical.cert-manager.application.certificate.issuance` | `cert-manager.application.certificate.issuance` |-| Renewal | `com.infisical.cert-manager.application.certificate.renewal` | `cert-manager.application.certificate.renewal` |-| Revocation | `com.infisical.cert-manager.application.certificate.revocation` | `cert-manager.application.certificate.revocation` |+| Event | Application alert `type` | Certificate Manager alert `type` |+|-------|--------------------------|----------------------------------|+| Expiration | `com.infisical.cert-manager.application.certificate.expiry` | `com.infisical.cert-manager.certificate.expiry` |+| Issuance | `com.infisical.cert-manager.application.certificate.issuance` | `com.infisical.cert-manager.certificate.issuance` |+| Renewal | `com.infisical.cert-manager.application.certificate.renewal` | `com.infisical.cert-manager.certificate.renewal` |+| Revocation | `com.infisical.cert-manager.application.certificate.revocation` | `com.infisical.cert-manager.certificate.revocation` |+| Signer certificate expiration | Not available | `com.infisical.cert-manager.signer.certificate.expiry` |++The `subject` field is the same value without the `com.infisical.` prefix.## Webhook payload format`data.items` lists the certificates the alert fired for. Each item has the certificate's ID, a `title` (its common name, or its first SAN or serial number when it has none), a one-line `summary`, a `severity`, and a list of display `fields`. To act on a certificate in code, read `resource` instead of `fields`: it holds the certificate's typed values, with ISO 8601 dates and the raw revocation reason code. An expiration request can include several certificates, and `data.alert.condition` holds the alert's lead time as you entered it, such as `30d` or `2w`. Issuance, renewal, and revocation requests include the one certificate the event was about.+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.signer`: a signer certificate expiration alert, whose items list the signers in `resource.signerIds` and `resource.signerNames`+<Note>- Only alerts created in an application send this payload. 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.+ 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.</Note><Tabs><Tab title="Expiration">- ```json+ ```json expandable{"specversion": "1.0","type": "com.infisical.cert-manager.application.certificate.expiry",@@ -104,7 +129,7 @@ Each request is a [CloudEvents](https://cloudevents.io/) JSON payload. The `type<Tab title="Revocation">Revocation items also include a **Revocation Reason** field. Issuance and renewal requests have the same shape without that field.- ```json+ ```json expandable{"specversion": "1.0","type": "com.infisical.cert-manager.application.certificate.revocation",@@ -157,6 +182,110 @@ Each request is a [CloudEvents](https://cloudevents.io/) JSON payload. The `type}```</Tab>+ <Tab title="Certificate Manager alert">+ A Certificate Manager alert sends the same payload as an application alert, with `resourceType` set to `cert-manager`. This example shows a revocation:++ ```json expandable+ {+ "specversion": "1.0",+ "type": "com.infisical.cert-manager.certificate.revocation",+ "source": "/alerts/453421e2-2e73-4700-92c8-60ccd3e7073e",+ "id": "8360c717-097a-4592-a2b0-63c494c3b558",+ "time": "2026-10-05T21:37:35.935Z",+ "datacontenttype": "application/json",+ "subject": "cert-manager.certificate.revocation",+ "data": {+ "alert": {+ "id": "453421e2-2e73-4700-92c8-60ccd3e7073e",+ "name": "prod-revocations",+ "resourceType": "cert-manager"+ },+ "items": [+ {+ "id": "4f70e08e-ad7a-4f94-ac16-241126ab88ed",+ "title": "api.example.com",+ "summary": "Certificate 'api.example.com' was revoked in application 'payments-api'",+ "severity": "warning",+ "fields": [+ { "label": "Serial Number", "value": "77c2b1368a7dd4a8442c61d51d20cbdb2060a1e5" },+ { "label": "Profile", "value": "tls-server" },+ { "label": "Application", "value": "payments-api" },+ { "label": "Expires", "value": "November 4, 2026 at 09:37 PM UTC" },+ { "label": "Revocation Reason", "value": "Unspecified" }+ ],+ "resource": {+ "id": "4f70e08e-ad7a-4f94-ac16-241126ab88ed",+ "serialNumber": "77c2b1368a7dd4a8442c61d51d20cbdb2060a1e5",+ "commonName": "api.example.com",+ "altNames": [],+ "status": "revoked",+ "notBefore": "2026-10-05T21:37:28.426Z",+ "notAfter": "2026-11-04T21:37:28.426Z",+ "revokedAt": "2026-10-05T21:37:30.299Z",+ "revocationReason": 0,+ "profileId": "8d04ef1b-67cd-4021-8da4-b3096d11133b",+ "profileName": "tls-server",+ "applicationId": "d6e7232b-ffa5-48bf-9133-4731c6d001a0",+ "applicationName": "payments-api"+ }+ }+ ],+ "metadata": {+ "totalItems": 1,+ "viewUrl": "https://app.infisical.com/organizations/<org-id>/cert-manager/inventory"+ }+ }+ }+ ```+ </Tab>+ <Tab title="Signer certificate expiration">+ ```json expandable+ {+ "specversion": "1.0",+ "type": "com.infisical.cert-manager.signer.certificate.expiry",+ "source": "/alerts/9b3c1d2e-5f6a-4b7c-8d9e-0f1a2b3c4d5e",+ "id": "2c4e6a8b-1d3f-4a5c-9e7b-0d2f4a6c8e1b",+ "time": "2026-10-05T00:05:00.000Z",+ "datacontenttype": "application/json",+ "subject": "cert-manager.signer.certificate.expiry",+ "data": {+ "alert": {+ "id": "9b3c1d2e-5f6a-4b7c-8d9e-0f1a2b3c4d5e",+ "name": "signer-expiry",+ "resourceType": "cert-manager.signer"+ },+ "items": [+ {+ "id": "7e1f3a5c-9b2d-4e6f-8a0c-1d3e5f7a9b2c",+ "title": "release signing",+ "summary": "Certificate 'release signing' of signer 'release-signer' expires on October 25, 2026 at 12:00 AM UTC",+ "severity": "warning",+ "fields": [+ { "label": "Signer", "value": "release-signer" },+ { "label": "Serial Number", "value": "0a1b2c3d4e5f60718293a4b5c6d7e8f901234567" },+ { "label": "Expires", "value": "October 25, 2026 at 12:00 AM UTC" }+ ],+ "resource": {+ "id": "7e1f3a5c-9b2d-4e6f-8a0c-1d3e5f7a9b2c",+ "serialNumber": "0a1b2c3d4e5f60718293a4b5c6d7e8f901234567",+ "commonName": "release signing",+ "altNames": [],+ "status": "active",+ "notBefore": "2025-10-25T00:00:00.000Z",+ "notAfter": "2026-10-25T00:00:00.000Z",+ "signerIds": ["3d5f7a9b-2c4e-4f6a-8b0d-1e3f5a7c9e2b"],+ "signerNames": ["release-signer"]+ }+ }+ ],+ "metadata": {+ "totalItems": 1,+ "viewUrl": "https://app.infisical.com/organizations/<org-id>/cert-manager/code-signing"+ }+ }+ }+ ```+ </Tab></Tabs>## Webhook signature verification@@ -199,20 +328,3 @@ function verifyWebhookSignature(header, body, secret) {);}```--## What's next?--<CardGroup cols={2}>- <Card title="Slack" icon="slack" iconType="brands" href="/documentation/platform/pki/applications/alerting/slack-alerts">- Send alerts to a Slack channel.- </Card>- <Card title="PagerDuty" icon="radio-tower" href="/documentation/platform/pki/applications/alerting/pagerduty-alerts">- Create incidents in PagerDuty.- </Card>- <Card title="Certificate syncs" icon="refresh-cw" href="/documentation/platform/pki/applications/certificate-syncs/overview">- Push certificates to cloud destinations.- </Card>- <Card title="Certificates" icon="list" href="/documentation/platform/pki/applications/certificates">- View and manage certificates.- </Card>-</CardGroup>diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/overview.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/overview.mdxindex 9865534251..53ad4af644 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/overview.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/overview.mdx@@ -4,12 +4,66 @@ sidebarTitle: "Overview"description: "Push certificates to AWS, Azure, Cloudflare, and other destinations."----Push certificates from your Application to external services automatically. When paired with auto-renewal, renewed certificates are synced to their destinations — keeping your infrastructure current without manual intervention.+Push certificates from your Application to external services automatically. When paired with auto-renewal, renewed certificates are synced to their destinations, so your infrastructure stays current without manual work.<Info>Certificate Syncs are configured per Application. Select which certificates to sync, then configure the destination.</Info>+## Supported destinations++<CardGroup cols={2}>+ <Card title="AWS ACM" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager">+ Import certificates into ACM for use with AWS services.+ </Card>+ <Card title="AWS ELB" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-elastic-load-balancer">+ Deploy certificates directly to ALB/NLB listeners.+ </Card>+ <Card title="AWS Secrets Manager" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-secrets-manager">+ Store certificates as secrets for application retrieval.+ </Card>+ <Card title="Azure Key Vault" icon="microsoft" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/azure-key-vault">+ Import certificates into Azure Key Vault.+ </Card>+ <Card title="Chef" icon="utensils" href="/documentation/platform/pki/applications/certificate-syncs/chef">+ Distribute certificates through Chef Infra data bags.+ </Card>+ <Card title="Cloudflare" icon="cloudflare" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/cloudflare-custom-certificate">+ Deploy custom SSL certificates to Cloudflare zones.+ </Card>+ <Card title="F5 BIG-IP" icon="server" href="/documentation/platform/pki/applications/certificate-syncs/f5-big-ip">+ Deploy certificates to F5 BIG-IP appliances and SSL profiles.+ </Card>+ <Card title="NetScaler" icon="server" href="/documentation/platform/pki/applications/certificate-syncs/netscaler">+ Deploy certificates to Citrix NetScaler ADC.+ </Card>+ <Card title="Palo Alto Networks" icon="shield" href="/documentation/platform/pki/applications/certificate-syncs/palo-alto-networks">+ Deploy certificates to PAN-OS firewalls and Panorama templates.+ </Card>+ <Card title="Palo Alto Networks SSL/TLS profile" icon="shield" href="/documentation/platform/pki/applications/certificate-syncs/palo-alto-networks-ssl-tls-profile">+ Point a PAN-OS SSL/TLS service profile at a synced certificate.+ </Card>+ <Card title="Kemp LoadMaster" icon="scale" href="/documentation/platform/pki/applications/certificate-syncs/kemp-loadmaster">+ Deploy certificates to Progress Kemp LoadMaster.+ </Card>+ <Card title="Linux Server" icon="linux" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/linux-server">+ Deploy certificates to Linux servers over SSH.+ </Card>+ <Card title="Windows Server" icon="windows" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/windows-server">+ Deploy certificates to Windows servers over WinRM.+ </Card>+ <Card title="Nutanix Prism Central" icon="server" href="/documentation/platform/pki/applications/certificate-syncs/nutanix-prism-central">+ Update SSL certificates on Nutanix clusters.+ </Card>+ <Card title="GCP Certificate Manager" icon="google" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/gcp-certificate-manager">+ Upload certificates for Google Cloud load balancers.+ </Card>+</CardGroup>++<Note>+ Need a destination that isn't listed? Contact [email protected] to request it.+</Note>+## How it works```mermaid@@ -56,60 +110,6 @@ flowchart LROnly certificates managed by Infisical are affected during sync operations. Certificates created directly in the destination service remain untouched.</Note>-## Supported destinations--<CardGroup cols={2}>- <Card title="AWS Certificate Manager" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-certificate-manager">- Import certificates into ACM for use with AWS services.- </Card>- <Card title="AWS Elastic Load Balancer" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-elastic-load-balancer">- Deploy certificates directly to ALB/NLB listeners.- </Card>- <Card title="AWS Secrets Manager" icon="aws" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/aws-secrets-manager">- Store certificates as secrets for application retrieval.- </Card>- <Card title="Azure Key Vault" icon="microsoft" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/azure-key-vault">- Import certificates into Azure Key Vault.- </Card>- <Card title="GCP Certificate Manager" icon="google" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/gcp-certificate-manager">- Upload certificates for Google Cloud load balancers.- </Card>- <Card title="Cloudflare" icon="cloudflare" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/cloudflare-custom-certificate">- Deploy custom SSL certificates to Cloudflare zones.- </Card>- <Card title="Chef Infra" icon="utensils" href="/documentation/platform/pki/applications/certificate-syncs/chef">- Distribute certificates via Chef data bags.- </Card>- <Card title="NetScaler" icon="server" href="/documentation/platform/pki/applications/certificate-syncs/netscaler">- Deploy certificates to Citrix NetScaler ADC.- </Card>- <Card title="Palo Alto Networks" icon="shield" href="/documentation/platform/pki/applications/certificate-syncs/palo-alto-networks">- Deploy certificates to PAN-OS firewalls and Panorama templates.- </Card>- <Card title="Palo Alto Networks SSL/TLS profile" icon="shield" href="/documentation/platform/pki/applications/certificate-syncs/palo-alto-networks-ssl-tls-profile">- Point a PAN-OS SSL/TLS service profile at a synced certificate.- </Card>- <Card title="Kemp LoadMaster" icon="scale" href="/documentation/platform/pki/applications/certificate-syncs/kemp-loadmaster">- Deploy certificates to Progress Kemp LoadMaster.- </Card>- <Card title="F5 BIG-IP" icon="server" href="/documentation/platform/pki/applications/certificate-syncs/f5-big-ip">- Deploy certificates to F5 BIG-IP appliances and SSL profiles.- </Card>- <Card title="Linux Server" icon="linux" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/linux-server">- Deploy certificates to Linux servers over SSH.- </Card>- <Card title="Windows Server" icon="windows" iconType="brands" href="/documentation/platform/pki/applications/certificate-syncs/windows-server">- Deploy certificates to Windows servers over WinRM.- </Card>- <Card title="Nutanix Prism Central" icon="server" href="/documentation/platform/pki/applications/certificate-syncs/nutanix-prism-central">- Update SSL certificates on Nutanix clusters.- </Card>-</CardGroup>--<Note>- Need a destination that isn't listed? Contact [email protected] to request it.-</Note>-## Creating a certificate sync<Steps>diff --git a/docs/documentation/platform/pki/applications/certificates.mdx b/docs/documentation/platform/pki/applications/certificates.mdxindex 8d4d564f93..87a987acf9 100644--- a/docs/documentation/platform/pki/applications/certificates.mdx+++ b/docs/documentation/platform/pki/applications/certificates.mdx@@ -1,6 +1,6 @@---title: "Certificates"-sidebarTitle: "Certificates"+sidebarTitle: "Issue and manage certificates"description: "View and manage the certificate inventory for your Application."---diff --git a/docs/documentation/platform/pki/applications/enrollment-methods/acme.mdx b/docs/documentation/platform/pki/applications/enrollment-methods/acme.mdxindex 32197b31d1..8fd082fa19 100644--- a/docs/documentation/platform/pki/applications/enrollment-methods/acme.mdx+++ b/docs/documentation/platform/pki/applications/enrollment-methods/acme.mdx@@ -31,6 +31,32 @@ Use the ACME enrollment method to request and renew certificates automatically u</Card></CardGroup>+## Guides++<CardGroup cols={2}>+ <Card title="Kubernetes (cert-manager)" icon="settings" href="/documentation/platform/pki/guides/applications/k8s-cert-manager-acme">+ Provision TLS certificates in Kubernetes with cert-manager's ACME issuer.+ </Card>+ <Card title="NGINX" icon="server" href="/documentation/platform/pki/guides/applications/nginx-certbot">+ Issue TLS certificates for NGINX with Certbot.+ </Card>+ <Card title="Apache" icon="server" href="/documentation/platform/pki/guides/applications/apache-certbot">+ Issue TLS certificates for Apache HTTP Server with Certbot.+ </Card>+ <Card title="Tomcat" icon="server" href="/documentation/platform/pki/guides/applications/tomcat-certbot">+ Issue TLS certificates for Apache Tomcat with Certbot.+ </Card>+ <Card title="JBoss/WildFly" icon="server" href="/documentation/platform/pki/guides/applications/jboss-certbot">+ Issue TLS certificates for JBoss or WildFly with Certbot.+ </Card>+ <Card title="Windows Server" icon="windows" iconType="brands" href="/documentation/platform/pki/guides/applications/windows-server-acme">+ Issue TLS certificates for Windows Server with win-acme.+ </Card>+ <Card title="Gloo Mesh" icon="workflow" href="/documentation/platform/pki/guides/applications/gloo-mesh">+ Provision Istio intermediate CA certificates for Gloo Mesh.+ </Card>+</CardGroup>+## PrerequisitesInstall an [ACME client](https://letsencrypt.org/docs/client-options/) on your server. The client handles domain validation challenges and certificate renewal.diff --git a/docs/documentation/platform/pki/applications/enrollment-methods/api.mdx b/docs/documentation/platform/pki/applications/enrollment-methods/api.mdxindex 7308709946..11a8bb3f84 100644--- a/docs/documentation/platform/pki/applications/enrollment-methods/api.mdx+++ b/docs/documentation/platform/pki/applications/enrollment-methods/api.mdx@@ -31,6 +31,20 @@ API enrollment is the default method for issuing certificates through the Infisi</Card></CardGroup>+## Guides++<CardGroup cols={2}>+ <Card title="Infisical Agent" icon="bot" href="/documentation/platform/pki/guides/applications/infisical-agent">+ Issue and renew certificates automatically with the Infisical Agent.+ </Card>+ <Card title="Infisical Agent reference" icon="book-open" href="/documentation/platform/pki/reference/infisical-agent">+ Every configuration option for the Agent's certificate management mode.+ </Card>+ <Card title="Kubernetes (Infisical Issuer)" icon="settings" href="/documentation/platform/pki/guides/applications/k8s-cert-manager-issuer">+ Issue and renew Kubernetes TLS certificates with the Infisical cert-manager issuer.+ </Card>+</CardGroup>+## Configure API enrollment<Steps>diff --git a/docs/documentation/platform/pki/applications/enrollment-methods/scep.mdx b/docs/documentation/platform/pki/applications/enrollment-methods/scep.mdxindex 0a742b366d..0d51d00cdb 100644--- a/docs/documentation/platform/pki/applications/enrollment-methods/scep.mdx+++ b/docs/documentation/platform/pki/applications/enrollment-methods/scep.mdx@@ -45,6 +45,17 @@ https://app.infisical.com/scep/{profile_id}/pkiclient.exeFor self-hosted Infisical instances, replace `app.infisical.com` with your instance's domain.+## Guides++<CardGroup cols={2}>+ <Card title="Jamf Pro" icon="smartphone" href="/documentation/platform/pki/guides/applications/jamf-pro-scep">+ Distribute certificates to devices that Jamf Pro manages.+ </Card>+ <Card title="Microsoft Intune" icon="windows" iconType="brands" href="/documentation/platform/pki/guides/applications/microsoft-intune-scep">+ Issue certificates to Intune-managed devices, with Intune validating every request.+ </Card>+</CardGroup>+## Prerequisites- A SCEP-compatible client (e.g., [sscep](https://github.com/certnanny/sscep)) or a network device with built-in SCEP support.diff --git a/docs/documentation/platform/pki/applications/overview.mdx b/docs/documentation/platform/pki/applications/overview.mdxindex da10236a66..072a882c70 100644--- a/docs/documentation/platform/pki/applications/overview.mdx+++ b/docs/documentation/platform/pki/applications/overview.mdx@@ -1,6 +1,5 @@---title: "Applications"-sidebarTitle: "Overview"description: "Issue certificates, configure enrollment, and manage lifecycle automation for your services."---diff --git a/docs/documentation/platform/pki/ca/digicert-direct.mdx b/docs/documentation/platform/pki/ca/digicert-direct.mdxindex ef7658eb1e..a49c811c73 100644--- a/docs/documentation/platform/pki/ca/digicert-direct.mdx+++ b/docs/documentation/platform/pki/ca/digicert-direct.mdx@@ -1,5 +1,6 @@---title: "DigiCert (CertCentral Services API)"+sidebarTitle: "DigiCert (CertCentral API)"description: "Issue TLS or Code Signing certificates from DigiCert using the CertCentral Services API."---diff --git a/docs/documentation/platform/pki/ca/digicert.mdx b/docs/documentation/platform/pki/ca/digicert.mdxindex 4e31368441..25c3289085 100644--- a/docs/documentation/platform/pki/ca/digicert.mdx+++ b/docs/documentation/platform/pki/ca/digicert.mdx@@ -1,5 +1,6 @@---title: "DigiCert"+sidebarTitle: "DigiCert (ACME)"description: "Learn how to connect Infisical to DigiCert to issue certificates via ACME."---diff --git a/docs/documentation/platform/pki/ca/external-ca.mdx b/docs/documentation/platform/pki/ca/external-ca.mdxindex c8c368e09d..1473ab38ef 100644--- a/docs/documentation/platform/pki/ca/external-ca.mdx+++ b/docs/documentation/platform/pki/ca/external-ca.mdx@@ -10,63 +10,53 @@ Integrate with External Certificate Authorities (CAs) to use existing PKI infrasThis page is for product admins setting up PKI infrastructure. Teams issuing certificates should see [Applications](/documentation/platform/pki/applications/overview).</Info>-```mermaid-graph TD- A1[External Public CA<br>e.g. Let's Encrypt, DigiCert] --> Infisical- A2[External Private CA<br>e.g. AWS Private CA, Venafi] --> Infisical-```+## Public CAs-## Types of external CAs--| Type | Examples | Use Case |-|------|----------|----------|-| **External Public CAs** | Let's Encrypt, DigiCert, Sectigo | Public-facing services with browser trust |-| **External Private CAs** | AWS Private CA, Venafi, Microsoft ADCS | Internal services, cloud-hosted or on-prem |--Infisical can act as an ACME client, allowing integration with any [ACME-compatible CA](/documentation/platform/pki/ca/acme-ca).--## Supported external CAs--### Public CAs+Public CAs issue certificates that browsers trust, for public-facing services:<CardGroup cols={2}>- <Card title="ACME CA (Generic)" icon="bot" href="/documentation/platform/pki/ca/acme-ca">- Connect to any ACME-compatible CA (Let's Encrypt, ZeroSSL, Buypass, etc.)+ <Card title="ACME-compatible CA" icon="bot" href="/documentation/platform/pki/ca/acme-ca">+ Connect to any CA that supports ACME, such as ZeroSSL or Buypass.</Card><Card title="Let's Encrypt" icon="lock" href="/documentation/platform/pki/ca/lets-encrypt">Free, automated certificates for public domains.</Card>- <Card title="AWS ACM Public CA" icon="aws" iconType="brands" href="/documentation/platform/pki/ca/aws-acm-public-ca">- Publicly trusted certificates via AWS Certificate Manager.+ <Card title="DigiCert (ACME)" icon="shield-check" href="/documentation/platform/pki/ca/digicert">+ DigiCert certificates through ACME with External Account Binding.</Card>- <Card title="DigiCert" icon="shield-check" href="/documentation/platform/pki/ca/digicert">- Enterprise certificates via DigiCert CertCentral.+ <Card title="DigiCert (CertCentral API)" icon="shield-half" href="/documentation/platform/pki/ca/digicert-direct">+ DigiCert TLS and code signing certificates through the CertCentral Services API.</Card>- <Card title="DigiCert Direct" icon="shield-half" href="/documentation/platform/pki/ca/digicert-direct">- Direct integration with DigiCert infrastructure.+ <Card title="GoDaddy" icon="globe" href="/documentation/platform/pki/ca/godaddy">+ Domain Validated certificates through the GoDaddy Certificates API.</Card><Card title="Sectigo" icon="award" href="/documentation/platform/pki/ca/sectigo">- Enterprise certificates via Sectigo Certificate Manager.+ Sectigo certificates through ACME with External Account Binding.+ </Card>+ <Card title="AWS ACM public CA" icon="aws" iconType="brands" href="/documentation/platform/pki/ca/aws-acm-public-ca">+ Publicly trusted certificates from AWS Certificate Manager.</Card></CardGroup>-### Private CAs+## Private CAs++Private CAs issue certificates for internal services, from PKI you already run in the cloud or on premises:<CardGroup cols={2}>- <Card title="AWS Private CA" icon="aws" iconType="brands" href="/documentation/platform/pki/ca/aws-pca">- Cloud-native private certificate management via AWS PCA.- </Card><Card title="Microsoft ADCS" icon="microsoft" iconType="brands" href="/documentation/platform/pki/ca/adcs">Microsoft AD CS over MS-WCCE through an Infisical Gateway.</Card>- <Card title="Azure ADCS (Web Enrollment)" icon="microsoft" iconType="brands" href="/documentation/platform/pki/ca/azure-adcs">+ <Card title="Azure ADCS (web enrollment)" icon="microsoft" iconType="brands" href="/documentation/platform/pki/ca/azure-adcs">Microsoft AD CS over HTTPS web enrollment.</Card>+ <Card title="AWS private CA" icon="aws" iconType="brands" href="/documentation/platform/pki/ca/aws-pca">+ Private certificates from AWS Private Certificate Authority.+ </Card><Card title="Venafi TLS Protect Cloud" icon="cloud" href="/documentation/platform/pki/ca/venafi">Venafi's cloud-based certificate management platform.</Card><Card title="Venafi TPP" icon="server" href="/documentation/platform/pki/ca/venafi-tpp">- Venafi Trust Protection Platform (on-premises).+ Venafi Trust Protection Platform, on premises.</Card></CardGroup>diff --git a/docs/documentation/platform/pki/ca/overview.mdx b/docs/documentation/platform/pki/ca/overview.mdxindex 0bea10f316..60a32278d3 100644--- a/docs/documentation/platform/pki/ca/overview.mdx+++ b/docs/documentation/platform/pki/ca/overview.mdx@@ -4,36 +4,33 @@ sidebarTitle: "Overview"description: "Set up Certificate Authorities to issue certificates across your organization."----A Certificate Authority (CA) is the entity that signs and issues X.509 certificates. Before teams can issue certificates through Applications, product admins need to configure at least one CA.--Certificate Manager supports two types of CAs:+A Certificate Authority (CA) signs and issues X.509 certificates. Before teams can issue certificates through applications, an admin needs to set up at least one CA, either in Infisical or by connecting one you already use.<CardGroup cols={2}>- <Card title="Private CA" icon="lock" href="/documentation/platform/pki/ca/private-ca">- **Managed by Infisical**-- Create root and intermediate CAs directly in Infisical. Ideal for internal services, mTLS, and private networks where public trust isn't required.+ <Card title="Internal CA" icon="lock" href="/documentation/platform/pki/ca/private-ca">+ Create root and intermediate CAs in Infisical for internal services, mTLS, and private networks.</Card><Card title="External CA" icon="landmark" href="/documentation/platform/pki/ca/external-ca">- **Integrated with Infisical**-- Connect to public CAs (Let's Encrypt, DigiCert) or enterprise PKI (AWS PCA, Microsoft ADCS, Venafi). Use existing infrastructure or issue publicly trusted certificates.+ Issue from a public CA such as Let's Encrypt or DigiCert, or from enterprise PKI such as AWS Private CA, Microsoft ADCS, or Venafi.+ </Card>+ <Card title="HSM connectors" icon="shield-half" href="/documentation/platform/pki/settings/hsm-connectors">+ Keep internal CA and signer keys in your own HSM.</Card></CardGroup>## Which should I use?-| Use Case | Recommended CA |+| Use case | Recommended CA ||----------|----------------|-| Internal services, mTLS between microservices | Private CA |+| Internal services, mTLS between microservices | Internal CA || Public-facing websites needing browser trust | External CA (Let's Encrypt, DigiCert) |-| Enterprise with existing PKI infrastructure | External CA (AWS PCA, Microsoft ADCS, Venafi) |-| IoT devices, internal device fleet | Private CA |+| Enterprise with existing PKI infrastructure | External CA (AWS Private CA, Microsoft ADCS, Venafi) |+| IoT devices, internal device fleet | Internal CA || Regulated environments with specific CA requirements | External CA (your approved provider) |-## Private CA hierarchy+## Internal CA hierarchy-When using Private CAs, you typically create a hierarchy:+When you use internal CAs, you typically create a hierarchy:```Root CA (offline, long-lived)@@ -42,53 +39,19 @@ Root CA (offline, long-lived)```<Info>- Best practice: Keep your Root CA offline or with minimal usage. Create one or more Intermediate CAs to issue day-to-day certificates. This limits exposure if an Intermediate CA is compromised.+ Keep your root CA offline or use it as little as possible. Create one or more intermediate CAs to issue day-to-day certificates, so a compromised intermediate CA doesn't expose the root.</Info>-## External CA integrations--Infisical integrates with major public and private CA providers:--<CardGroup cols={3}>- <Card title="Let's Encrypt" icon="lock" href="/documentation/platform/pki/ca/lets-encrypt">- Free, automated, publicly trusted certificates.- </Card>- <Card title="DigiCert" icon="shield-check" href="/documentation/platform/pki/ca/digicert">- Enterprise-grade public and private certificates.- </Card>- <Card title="AWS PCA" icon="aws" iconType="brands" href="/documentation/platform/pki/ca/aws-pca">- Private CA managed in AWS.- </Card>- <Card title="Microsoft ADCS" icon="microsoft" iconType="brands" href="/documentation/platform/pki/ca/adcs">- Active Directory Certificate Services over the Gateway.- </Card>- <Card title="Azure ADCS (Web Enrollment)" icon="microsoft" iconType="brands" href="/documentation/platform/pki/ca/azure-adcs">- Active Directory Certificate Services over HTTPS web enrollment.- </Card>- <Card title="Venafi" icon="building" href="/documentation/platform/pki/ca/venafi">- Enterprise certificate lifecycle management.- </Card>- <Card title="ACME CAs" icon="bot" href="/documentation/platform/pki/ca/acme-ca">- Any ACME-compatible CA.- </Card>-</CardGroup>--[View all External CA integrations →](/documentation/platform/pki/ca/external-ca)-## Next steps<Steps>- <Step title="Create or connect a CA">- Set up a [Private CA](/documentation/platform/pki/ca/private-ca) or connect an [External CA](/documentation/platform/pki/ca/external-ca).+ <Step>+ Set up an [internal CA](/documentation/platform/pki/ca/private-ca) or connect an [external CA](/documentation/platform/pki/ca/external-ca).</Step>- <Step title="Create a Certificate Policy">- Define the rules for certificates — allowed domains, validity periods, key algorithms.-- [Certificate Policies →](/documentation/platform/pki/settings/policies)+ <Step>+ Create a [certificate policy](/documentation/platform/pki/settings/policies) to set the domains, validity periods, and key algorithms that certificates can use.</Step>- <Step title="Create a Certificate Profile">- Combine your CA with a policy to create a reusable profile that teams can consume.-- [Certificate Profiles →](/documentation/platform/pki/settings/profiles)+ <Step>+ Create a [certificate profile](/documentation/platform/pki/settings/profiles) that pairs your CA with the policy, so applications can issue from it.</Step></Steps>diff --git a/docs/documentation/platform/pki/ca/private-ca.mdx b/docs/documentation/platform/pki/ca/private-ca.mdxindex f1d62b88a2..959cb9e010 100644--- a/docs/documentation/platform/pki/ca/private-ca.mdx+++ b/docs/documentation/platform/pki/ca/private-ca.mdx@@ -296,12 +296,18 @@ curl --location --request POST 'https://app.infisical.com/api/v1/cert-manager/ca## What's next?<CardGroup cols={2}>- <Card title="CA Renewal" icon="refresh-cw" href="/documentation/platform/pki/ca/ca-renewal">+ <Card title="CA renewal" icon="refresh-cw" href="/documentation/platform/pki/ca/ca-renewal">Renew your CA certificates before they expire.</Card>- <Card title="CRL Distribution Points" icon="list" href="/documentation/platform/pki/ca/crl-distribution">+ <Card title="CRL distribution" icon="list" href="/documentation/platform/pki/ca/crl-distribution">Configure CRL mirrors for high availability.</Card>+ <Card title="OCSP" icon="radio-tower" href="/documentation/platform/pki/ca/ocsp">+ Answer certificate revocation checks in real time.+ </Card>+ <Card title="Post-quantum algorithms" icon="atom" href="/documentation/platform/pki/reference/pqc-algorithms">+ Issue certificates with post-quantum signature algorithms.+ </Card></CardGroup><CardGroup cols={2}>diff --git a/docs/documentation/platform/pki/ca/venafi.mdx b/docs/documentation/platform/pki/ca/venafi.mdxindex 672a688a22..d79e5f7ab7 100644--- a/docs/documentation/platform/pki/ca/venafi.mdx+++ b/docs/documentation/platform/pki/ca/venafi.mdx@@ -1,6 +1,5 @@---title: "Venafi TLS Protect Cloud"-sidebarTitle: "Venafi"description: "Learn how to use Venafi TLS Protect Cloud as an external CA to sign internal intermediate CAs in Infisical."---diff --git a/docs/documentation/platform/pki/code-signing/overview.mdx b/docs/documentation/platform/pki/code-signing/overview.mdxindex 02ccb17f1e..27903d6a7f 100644--- a/docs/documentation/platform/pki/code-signing/overview.mdx+++ b/docs/documentation/platform/pki/code-signing/overview.mdx@@ -4,12 +4,25 @@ sidebarTitle: "Overview"description: "Sign software artifacts with managed code-signing certificates, central approval, and a full audit trail."----Code Signing is where teams digitally sign software (JARs, container images, Windows installers, Android APKs, Linux packages, scripts). Within Code Signing, you can:+Code Signing is where teams digitally sign software, such as JARs, container images, Windows installers, Android APKs, Linux packages, and scripts. Teams sign through any tool that supports PKCS#11, with Windows `signtool`, or with the [Sign API](/api-reference/endpoints/code-signing/signers/sign), and Infisical records every signing operation in an audit trail.-- **Sign artifacts** through any tool that supports PKCS#11, with native Windows `signtool`, or directly via the [Sign API](/api-reference/endpoints/code-signing/signers/sign)-- **Require approvals** before signatures are produced, with per-approval limits on count and time-- **Manage who can sign** with per-Signer roles for users, machine identities, and groups-- **Track every signing operation** in a full audit trail+<CardGroup cols={2}>+ <Card title="Signers" icon="pen-tool" href="/documentation/platform/pki/code-signing/signers">+ Create signing identities and choose who can sign with each one.+ </Card>+ <Card title="Approvals" icon="check-check" href="/documentation/platform/pki/code-signing/approvals">+ Require approval before someone can sign, with limits on how many signatures and for how long.+ </Card>+ <Card title="Signing tools" icon="wrench" href="/documentation/platform/pki/guides/code-signing/jarsigner">+ Sign with jarsigner, apksigner, osslsigncode, cosign, OpenSSL, or GPG.+ </Card>+ <Card title="PKCS#11 module" icon="cpu" href="/documentation/platform/pki/code-signing/pkcs11-module">+ Connect standard signing tools to your signers.+ </Card>+ <Card title="Windows KSP" icon="windows" iconType="brands" href="/documentation/platform/pki/code-signing/windows-ksp">+ Sign Windows executables, DLLs, and MSIs with signtool.+ </Card>+</CardGroup>Each **Signer** represents a single signing identity, like `mobile-app-prod`, `firmware-release`, or `ci-staging-builds`. Product Admins create Signers, attach a code-signing certificate, and assign team members. Teams then operate independently within their assigned Signers.diff --git a/docs/documentation/platform/pki/code-signing/signers.mdx b/docs/documentation/platform/pki/code-signing/signers.mdxindex 0d8c2de601..6a3fd3bc0d 100644--- a/docs/documentation/platform/pki/code-signing/signers.mdx+++ b/docs/documentation/platform/pki/code-signing/signers.mdx@@ -204,6 +204,9 @@ To sign with a Signer, pick the integration that matches your tooling:## What's next?<CardGroup cols={2}>+ <Card title="DigiCert" icon="shield-check" href="/documentation/platform/pki/guides/code-signing/digicert-code-signing">+ Issue a signer's certificate from DigiCert CertCentral with an HSM-backed key.+ </Card><Card title="Approvals" icon="check-check" href="/documentation/platform/pki/code-signing/approvals">Add approval steps and per-approval limits to a Signer.</Card>diff --git a/docs/documentation/platform/pki/getting-started.mdx b/docs/documentation/platform/pki/getting-started.mdxdeleted file mode 100644index cb97ae7152..0000000000--- a/docs/documentation/platform/pki/getting-started.mdx+++ /dev/null@@ -1,22 +0,0 @@-----title: "Quickstarts"-sidebarTitle: "Getting started"-description: "Get started with Infisical Certificate Manager."------Infisical Certificate Manager lets you issue X.509 certificates and sign code artifacts. Choose a quick start to get up and running:--<CardGroup cols={2}>- <Card title="Issue Your First Certificate" icon="award" href="/documentation/platform/pki/quick-starts/issue-first-certificate">- Get a TLS certificate in under 10 minutes.- </Card>- <Card title="Sign Your First Artifact" icon="file-pen" href="/documentation/platform/pki/quick-starts/sign-first-code">- Sign a JAR file in under 10 minutes.- </Card>-</CardGroup>--Once you have issued a certificate by hand, the [Reference Architecture](/documentation/platform/pki/concepts/reference-architecture) shows how your CAs, issuance rules, and enrollment paths lay out across your teams and environments.--<Tip>- New to PKI? Read the [Overview](/documentation/platform/pki/overview) to understand how Certificate Manager works.-</Tip>diff --git a/docs/documentation/platform/pki/guides/applications/apache-certbot.mdx b/docs/documentation/platform/pki/guides/applications/apache-certbot.mdxindex 050e557141..643b48efe9 100644--- a/docs/documentation/platform/pki/guides/applications/apache-certbot.mdx+++ b/docs/documentation/platform/pki/guides/applications/apache-certbot.mdx@@ -1,6 +1,6 @@---title: "Apache with Certbot"-sidebarTitle: "Set up HTTPS for Apache"+sidebarTitle: "Apache"description: "Issue TLS certificates for Apache HTTP Server using ACME enrollment with Certbot."---diff --git a/docs/documentation/platform/pki/guides/applications/gloo-mesh.mdx b/docs/documentation/platform/pki/guides/applications/gloo-mesh.mdxindex 0fe2e7910b..c7295a5995 100644--- a/docs/documentation/platform/pki/guides/applications/gloo-mesh.mdx+++ b/docs/documentation/platform/pki/guides/applications/gloo-mesh.mdx@@ -1,6 +1,6 @@---title: "Gloo Mesh"-sidebarTitle: "Configure Gloo Mesh certificates"+sidebarTitle: "Gloo Mesh"description: "Provision Istio intermediate CA certificates for Gloo Mesh using Infisical."---diff --git a/docs/documentation/platform/pki/guides/applications/infisical-agent.mdx b/docs/documentation/platform/pki/guides/applications/infisical-agent.mdxindex abfe1ed32b..43522b9ea7 100644--- a/docs/documentation/platform/pki/guides/applications/infisical-agent.mdx+++ b/docs/documentation/platform/pki/guides/applications/infisical-agent.mdx@@ -1,6 +1,6 @@---title: "Automate certificates with Infisical Agent"-sidebarTitle: "Automate certificate renewal"+sidebarTitle: "Infisical Agent"description: "Set up automatic certificate management using the Infisical Agent."---diff --git a/docs/documentation/platform/pki/guides/applications/jamf-pro-scep.mdx b/docs/documentation/platform/pki/guides/applications/jamf-pro-scep.mdxindex 76708f9d18..01cb9785a0 100644--- a/docs/documentation/platform/pki/guides/applications/jamf-pro-scep.mdx+++ b/docs/documentation/platform/pki/guides/applications/jamf-pro-scep.mdx@@ -1,6 +1,6 @@---title: "Jamf Pro with SCEP"-sidebarTitle: "Enroll devices with Jamf Pro"+sidebarTitle: "Jamf Pro"description: "Distribute certificates to managed devices using Infisical SCEP enrollment with Jamf Pro."---diff --git a/docs/documentation/platform/pki/guides/applications/jboss-certbot.mdx b/docs/documentation/platform/pki/guides/applications/jboss-certbot.mdxindex d65738d5d8..6602d0fc93 100644--- a/docs/documentation/platform/pki/guides/applications/jboss-certbot.mdx+++ b/docs/documentation/platform/pki/guides/applications/jboss-certbot.mdx@@ -1,6 +1,6 @@---title: "JBoss/WildFly with Certbot"-sidebarTitle: "Set up HTTPS for JBoss"+sidebarTitle: "JBoss/WildFly"description: "Issue TLS certificates for JBoss/WildFly using ACME enrollment with Certbot."---diff --git a/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-acme.mdx b/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-acme.mdxindex 9a941a323f..147d393fb8 100644--- a/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-acme.mdx+++ b/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-acme.mdx@@ -1,6 +1,6 @@---title: "Kubernetes with cert-manager (ACME)"-sidebarTitle: "Issue TLS certificates in Kubernetes (ACME)"+sidebarTitle: "Kubernetes (cert-manager)"description: "Automatically provision and manage TLS certificates in Kubernetes using cert-manager's ACME issuer and Infisical."---diff --git a/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-issuer.mdx b/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-issuer.mdxindex 5aac81d957..6a81e21245 100644--- a/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-issuer.mdx+++ b/docs/documentation/platform/pki/guides/applications/k8s-cert-manager-issuer.mdx@@ -1,6 +1,6 @@---title: "Kubernetes with cert-manager (Infisical Issuer)"-sidebarTitle: "Issue TLS certificates in Kubernetes (Infisical Issuer)"+sidebarTitle: "Kubernetes (Infisical Issuer)"description: "Issue and renew Kubernetes TLS certificates with the Infisical cert-manager external issuer, authenticating with a machine identity."---diff --git a/docs/documentation/platform/pki/guides/applications/microsoft-intune-scep.mdx b/docs/documentation/platform/pki/guides/applications/microsoft-intune-scep.mdxindex 3571f84d71..8e238ed2b1 100644--- a/docs/documentation/platform/pki/guides/applications/microsoft-intune-scep.mdx+++ b/docs/documentation/platform/pki/guides/applications/microsoft-intune-scep.mdx@@ -1,6 +1,6 @@---title: "Microsoft Intune with SCEP"-sidebarTitle: "Enroll devices with Microsoft Intune"+sidebarTitle: "Microsoft Intune"description: "Issue certificates to Microsoft Intune-managed devices over SCEP, with Intune validating every request before Infisical signs it."---diff --git a/docs/documentation/platform/pki/guides/applications/nginx-certbot.mdx b/docs/documentation/platform/pki/guides/applications/nginx-certbot.mdxindex 9ac001b9c7..07c7db3134 100644--- a/docs/documentation/platform/pki/guides/applications/nginx-certbot.mdx+++ b/docs/documentation/platform/pki/guides/applications/nginx-certbot.mdx@@ -1,6 +1,6 @@---title: "NGINX with Certbot"-sidebarTitle: "Set up HTTPS for NGINX"+sidebarTitle: "NGINX"description: "Issue TLS certificates for NGINX using ACME enrollment with Certbot."---diff --git a/docs/documentation/platform/pki/guides/applications/tomcat-certbot.mdx b/docs/documentation/platform/pki/guides/applications/tomcat-certbot.mdxindex 871722ca90..fe3b1c8e34 100644--- a/docs/documentation/platform/pki/guides/applications/tomcat-certbot.mdx+++ b/docs/documentation/platform/pki/guides/applications/tomcat-certbot.mdx@@ -1,6 +1,6 @@---title: "Tomcat with Certbot"-sidebarTitle: "Set up HTTPS for Tomcat"+sidebarTitle: "Tomcat"description: "Issue TLS certificates for Apache Tomcat using ACME enrollment with Certbot."---diff --git a/docs/documentation/platform/pki/guides/applications/windows-server-acme.mdx b/docs/documentation/platform/pki/guides/applications/windows-server-acme.mdxindex 067cff60ad..8fb44d5fd0 100644--- a/docs/documentation/platform/pki/guides/applications/windows-server-acme.mdx+++ b/docs/documentation/platform/pki/guides/applications/windows-server-acme.mdx@@ -1,6 +1,6 @@---title: "Windows Server with win-acme"-sidebarTitle: "Set up HTTPS for Windows"+sidebarTitle: "Windows Server"description: "Issue TLS certificates for Windows Server using ACME enrollment with win-acme."---diff --git a/docs/documentation/platform/pki/guides/code-signing/apksigner.mdx b/docs/documentation/platform/pki/guides/code-signing/apksigner.mdxindex 7ae69fcf6b..2d09263280 100644--- a/docs/documentation/platform/pki/guides/code-signing/apksigner.mdx+++ b/docs/documentation/platform/pki/guides/code-signing/apksigner.mdx@@ -1,6 +1,6 @@---title: "Sign Android APKs with apksigner"-sidebarTitle: "Sign Android APKs"+sidebarTitle: "apksigner"description: "Use the Infisical PKCS#11 module to sign Android APK and AAB files with apksigner."---diff --git a/docs/documentation/platform/pki/guides/code-signing/cosign.mdx b/docs/documentation/platform/pki/guides/code-signing/cosign.mdxindex a0aeec9402..14ec3edc64 100644--- a/docs/documentation/platform/pki/guides/code-signing/cosign.mdx+++ b/docs/documentation/platform/pki/guides/code-signing/cosign.mdx@@ -1,6 +1,6 @@---title: "Sign container images with cosign"-sidebarTitle: "Sign container images"+sidebarTitle: "cosign"description: "Use the Infisical PKCS#11 module to sign OCI container images with Sigstore cosign."---diff --git a/docs/documentation/platform/pki/guides/code-signing/digicert-code-signing.mdx b/docs/documentation/platform/pki/guides/code-signing/digicert-code-signing.mdxindex ef6dd074c0..dbdfccec1d 100644--- a/docs/documentation/platform/pki/guides/code-signing/digicert-code-signing.mdx+++ b/docs/documentation/platform/pki/guides/code-signing/digicert-code-signing.mdx@@ -1,6 +1,6 @@---title: "Sign with DigiCert"-sidebarTitle: "Sign with DigiCert"+sidebarTitle: "DigiCert"description: "Issue code-signing certificates from DigiCert CertCentral with an HSM-backed key."---diff --git a/docs/documentation/platform/pki/guides/code-signing/gpg.mdx b/docs/documentation/platform/pki/guides/code-signing/gpg.mdxindex 98d4582ea5..f574f2f6e2 100644--- a/docs/documentation/platform/pki/guides/code-signing/gpg.mdx+++ b/docs/documentation/platform/pki/guides/code-signing/gpg.mdx@@ -1,6 +1,6 @@---title: "Sign Git commits and tags with GPG"-sidebarTitle: "Sign Git commits with GPG"+sidebarTitle: "GPG"description: "Use the Infisical PKCS#11 module with GnuPG to sign git commits, tags, and packages."---diff --git a/docs/documentation/platform/pki/guides/code-signing/jarsigner.mdx b/docs/documentation/platform/pki/guides/code-signing/jarsigner.mdxindex 06a676db10..c6d4ab2e21 100644--- a/docs/documentation/platform/pki/guides/code-signing/jarsigner.mdx+++ b/docs/documentation/platform/pki/guides/code-signing/jarsigner.mdx@@ -1,6 +1,6 @@---title: "Sign JARs with jarsigner"-sidebarTitle: "Sign Java JARs"+sidebarTitle: "jarsigner"description: "Use the Infisical PKCS#11 module to sign Java artifacts with jarsigner."---diff --git a/docs/documentation/platform/pki/guides/code-signing/openssl.mdx b/docs/documentation/platform/pki/guides/code-signing/openssl.mdxindex 59f6858aef..c7c4bce822 100644--- a/docs/documentation/platform/pki/guides/code-signing/openssl.mdx+++ b/docs/documentation/platform/pki/guides/code-signing/openssl.mdx@@ -1,6 +1,6 @@---title: "Sign with OpenSSL"-sidebarTitle: "Sign files with OpenSSL"+sidebarTitle: "OpenSSL"description: "Use the Infisical PKCS#11 module with OpenSSL's pkcs11 engine for general-purpose signing."---diff --git a/docs/documentation/platform/pki/guides/code-signing/osslsigncode.mdx b/docs/documentation/platform/pki/guides/code-signing/osslsigncode.mdxindex 35f47023dc..2663026293 100644--- a/docs/documentation/platform/pki/guides/code-signing/osslsigncode.mdx+++ b/docs/documentation/platform/pki/guides/code-signing/osslsigncode.mdx@@ -1,6 +1,6 @@---title: "Sign Windows executables with osslsigncode"-sidebarTitle: "Sign Windows executables"+sidebarTitle: "osslsigncode"description: "Use the Infisical PKCS#11 module to sign Windows executables, DLLs, and MSI installers with osslsigncode."---diff --git a/docs/documentation/platform/pki/guides/overview.mdx b/docs/documentation/platform/pki/guides/overview.mdxdeleted file mode 100644index 3e22df017c..0000000000--- a/docs/documentation/platform/pki/guides/overview.mdx+++ /dev/null@@ -1,68 +0,0 @@-----title: "Guides"-sidebarTitle: "Overview"-description: "End-to-end guides for certificate issuance and code signing workflows."------Guides walk you through complete workflows, from start to finish.--## Certificate issuance guides--<CardGroup cols={2}>- <Card title="Automate Certificate Renewal" icon="bot" href="/documentation/platform/pki/guides/applications/infisical-agent">- Set up the Infisical Agent for automatic certificate management.- </Card>- <Card title="Issue TLS Certificates in Kubernetes (ACME)" icon="settings" href="/documentation/platform/pki/guides/applications/k8s-cert-manager-acme">- Issue certificates in Kubernetes with cert-manager's ACME issuer.- </Card>- <Card title="Issue TLS Certificates in Kubernetes (Infisical Issuer)" icon="settings" href="/documentation/platform/pki/guides/applications/k8s-cert-manager-issuer">- Issue certificates in Kubernetes with a machine identity via the Infisical Issuer.- </Card>- <Card title="Set Up HTTPS for NGINX" icon="server" href="/documentation/platform/pki/guides/applications/nginx-certbot">- ACME certificates with Certbot for NGINX.- </Card>- <Card title="Set Up HTTPS for Apache" icon="server" href="/documentation/platform/pki/guides/applications/apache-certbot">- ACME certificates with Certbot for Apache.- </Card>- <Card title="Set Up HTTPS for Tomcat" icon="server" href="/documentation/platform/pki/guides/applications/tomcat-certbot">- ACME certificates with Certbot for Tomcat.- </Card>- <Card title="Set Up HTTPS for JBoss" icon="server" href="/documentation/platform/pki/guides/applications/jboss-certbot">- ACME certificates with Certbot for JBoss/WildFly.- </Card>- <Card title="Set Up HTTPS for Windows" icon="windows" iconType="brands" href="/documentation/platform/pki/guides/applications/windows-server-acme">- ACME certificates for Windows Server with win-acme.- </Card>- <Card title="Configure Gloo Mesh Certificates" icon="workflow" href="/documentation/platform/pki/guides/applications/gloo-mesh">- Provision Istio intermediate CA certificates for service mesh.- </Card>- <Card title="Enroll Devices with Jamf Pro" icon="smartphone" href="/documentation/platform/pki/guides/applications/jamf-pro-scep">- Distribute certificates to managed devices via SCEP.- </Card>- <Card title="Enroll Devices with Microsoft Intune" icon="windows" iconType="brands" href="/documentation/platform/pki/guides/applications/microsoft-intune-scep">- Issue certificates to Intune-managed devices via SCEP.- </Card>-</CardGroup>--## Code signing guides--<CardGroup cols={2}>- <Card title="Sign Java JARs" icon="java" iconType="brands" href="/documentation/platform/pki/guides/code-signing/jarsigner">- Use jarsigner with the PKCS#11 module.- </Card>- <Card title="Sign Android APKs" icon="android" iconType="brands" href="/documentation/platform/pki/guides/code-signing/apksigner">- Use apksigner with the PKCS#11 module.- </Card>- <Card title="Sign Windows Executables" icon="windows" iconType="brands" href="/documentation/platform/pki/guides/code-signing/osslsigncode">- Use osslsigncode with the PKCS#11 module.- </Card>- <Card title="Sign Container Images" icon="docker" iconType="brands" href="/documentation/platform/pki/guides/code-signing/cosign">- Use Cosign with the PKCS#11 module.- </Card>- <Card title="Sign Files with OpenSSL" icon="lock" href="/documentation/platform/pki/guides/code-signing/openssl">- Use OpenSSL with the PKCS#11 module.- </Card>- <Card title="Sign Git Commits with GPG" icon="key" href="/documentation/platform/pki/guides/code-signing/gpg">- Use GPG with the PKCS#11 module.- </Card>-</CardGroup>diff --git a/docs/documentation/platform/pki/migration.mdx b/docs/documentation/platform/pki/migration.mdxindex d9159416bc..66066c16fb 100644--- a/docs/documentation/platform/pki/migration.mdx+++ b/docs/documentation/platform/pki/migration.mdx@@ -1,11 +1,11 @@---title: "Project migration guide"-sidebarTitle: "Project migration"+sidebarTitle: "Migrate to applications"description: "Migrate from the legacy project-based model to the new Application-centric model."---<Warning>- This guide is for existing customers on the legacy project-based model. If you're new to Infisical Certificate Manager, start with [Getting Started](/documentation/platform/pki/getting-started).+ This guide is for existing customers on the legacy project-based model. If you're new to Infisical Certificate Manager, start with the [Certificate management overview](/documentation/platform/pki/overview).</Warning>## What changeddiff --git a/docs/documentation/platform/pki/monitoring/certificate-inventory.mdx b/docs/documentation/platform/pki/monitoring/certificate-inventory.mdxnew file mode 100644index 0000000000..9336e4e13c--- /dev/null+++ b/docs/documentation/platform/pki/monitoring/certificate-inventory.mdx@@ -0,0 +1,153 @@+---+title: "Certificate inventory"+description: "Search, filter, and save views of every certificate in Certificate Manager."+---++The certificate inventory lists every certificate in Certificate Manager in one table: certificates issued through [Applications](/documentation/platform/pki/applications/overview), certificates you [import](/documentation/platform/pki/applications/certificates#importing-certificates), and certificates that [discovery](/documentation/platform/pki/discovery/overview) finds on your network. Use the inventory to find certificates that are about to expire, that have a key you want to retire, or that don't belong to an application yet.++## Prerequisites++- The Certificate Manager **Admin** role (see [access control](/documentation/platform/pki/concepts/access-control#product-level))++If you don't have the **Admin** role, you can see the certificates in your applications on each application's [**Certificates** tab](/documentation/platform/pki/applications/certificates).++## Find a certificate++Go to **Certificate Manager** > **Inventory**, then enter the certificate's SAN, common name, ID, or serial number in the search box.++### Columns++The **Health** column shows **Healthy** until 60 days before a certificate expires. After that, the column shows the time left, then **Expired**.++The **Application** and **Source** columns are hidden by default. To show or hide a column, select the columns button at the end of the toolbar. Infisical remembers your choice in this browser.++## Filter certificates++To filter the inventory:++<Steps>+ <Step>+ Select the filter button next to the search box.+ </Step>+ <Step>+ Select **Add filter**, then choose a field, an operator, and a value. Repeat for each filter you need.+ </Step>+ <Step>+ Select **Apply Filters**.+ </Step>+</Steps>++| Filter | What it matches |+| --- | --- |+| **Status** | Active, Renewed, Expired, or Revoked |+| **Expiration Date** | Certificates that expire before or after a date |+| **Issued Date** | Certificates whose validity starts before or after a date |+| **Enrollment Method** | The [enrollment method](/documentation/platform/pki/applications/enrollment-methods/overview) used to request the certificate: ACME, API, EST, or SCEP |+| **Algorithm** | RSA-2048, RSA-3072, RSA-4096, ECDSA-P256, ECDSA-P384, ECDSA-P521, or one of the [post-quantum](/documentation/platform/pki/reference/pqc-algorithms) algorithms ML-DSA-44, ML-DSA-65, and ML-DSA-87 |+| **Key Size** | 256, 384, or 521 bits for ECDSA keys, and 2048, 3072, or 4096 bits for RSA keys |+| **Source** | Managed (issued through Certificate Manager), Discovered (found by a discovery scan), or Imported |+| **Certificate Authority** | The [CA](/documentation/platform/pki/ca/overview) that issued the certificate |+| **Profile** | The [certificate profile](/documentation/platform/pki/settings/profiles) used to issue the certificate |+| **Application** | The application the certificate belongs to |+| **Metadata** | A metadata key on the certificate, and optionally the key's value |++A certificate appears only if it matches every filter. If you pick several values in one filter, a certificate matches if it has any of them.++The filters you apply appear as labels above the table. To remove one filter, select the **x** on its label. To remove them all, select **Clear all**.++## Views++A view is a saved set of filters. The views menu next to the filter button shows the view you're using, which is **All Certificates** by default. The menu groups views into:++- **System Views**: views that come with Certificate Manager+- **Shared Views**: views that an admin saved and shared with other admins+- **My Views**: views you saved for yourself++Infisical reopens the last view you used in this browser.++### Built-in views++| View | Shows |+| --- | --- |+| **All Certificates** | Every certificate |+| **Expiring in 7 days** | Active certificates that expire in the next 7 days |+| **Expiring in 30 days** | Active certificates that expire in the next 30 days |+| **Renewed** | Certificates that a [renewal](/documentation/platform/pki/applications/certificate-renewal) replaced with a new certificate |+| **Expired** | Certificates past their expiration date |+| **Revoked** | Certificates that were revoked |+| **Post-Quantum (PQC)** | Certificates with an ML-DSA key |+| **Classical (Non-PQC)** | Certificates with an RSA or ECDSA key |++### Save a view++To save the filters you use often:++<Steps>+ <Step>+ Select the filter button and add the filters you want to save.+ </Step>+ <Step>+ Select **Save as View...** and enter a name.+ </Step>+ <Step>+ To let other admins use the view, turn on **Share with team**.+ </Step>+ <Step>+ Select **Save**.+ </Step>+</Steps>++A view saves only filters. It doesn't save the search text or the columns you chose. You can't change a saved view's filters, so to change a view, save a new one and delete the old one.++Each shared view needs a unique name, and so does each of your personal views.++### Share or delete a view++Only the admin who saved a view can share it, make it personal again, or delete it. The menu doesn't offer these options for the view you're using, so switch to another view first.++<Steps>+ <Step>+ Open the views menu and hold the pointer over the view.+ </Step>+ <Step>+ Select the share icon (**Share with team** or **Make personal**), or select **Delete view** and confirm.+ </Step>+</Steps>++### Views in an application++Each application's **Certificates** tab has the same search, filters, and views, limited to that application's certificates. Views saved in an application appear only in that application, and views saved in the inventory don't appear in any application. The **Application** filter is available only in the inventory.++## Assign a certificate to an application++If a certificate you imported or discovered doesn't belong to an application yet, you can assign it to one so the application's members can manage it.++<Warning>+ You can't move a certificate to a different application after you assign it.+</Warning>++<Steps>+ <Step>+ In the certificate's row, select the options menu, then select **Assign to Application**.+ </Step>+ <Step>+ Select the application, then select **Assign**.+ </Step>+</Steps>++If a certificate already belongs to an application, revoke or delete it from that application's [**Certificates** tab](/documentation/platform/pki/applications/certificates).++## Export certificates++To download the certificates in the table as a CSV file, select the download button in the toolbar. The file includes only the certificates on the current page, so increase the number of rows per page before you export a longer list.++## Next steps++<CardGroup cols={2}>+ <Card title="Discovery" icon="radar" href="/documentation/platform/pki/discovery/overview">+ Scan your network to add certificates that Infisical didn't issue.+ </Card>+ <Card title="Alerts" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">+ Get notified before certificates expire.+ </Card>+</CardGroup>diff --git a/docs/documentation/platform/pki/overview.mdx b/docs/documentation/platform/pki/overview.mdxindex a724d83cb8..5b493cc96c 100644--- a/docs/documentation/platform/pki/overview.mdx+++ b/docs/documentation/platform/pki/overview.mdx@@ -1,68 +1,116 @@---title: "Certificate management"-description: "Manage Certificate Authorities and automate X.509 certificate lifecycle management across your organization."+description: "Issue, track, and renew X.509 certificates from internal or external CAs, and sign software artifacts."sidebarTitle: "Certificate Management"icon: "file-key"----Infisical Certificate Manager is a centralized platform for managing X.509 certificates across your organization. Issue certificates for TLS, mTLS, and device authentication — whether from your own private CAs or external providers like DigiCert and Let's Encrypt.+Infisical Certificate Manager issues X.509 certificates for TLS, mTLS, and device authentication, from your own private CAs or from external CAs such as DigiCert and Let's Encrypt. It also tracks every certificate in your organization, alerts you before certificates expire, and signs software artifacts.-The short video below provides a guided overview of Infisical's certificate management capabilities and key concepts, helping you build the right mental model before diving into the rest of the documentation.+<Warning>+ If you set up Certificate Manager before applications were introduced, see [Migrate to applications](/documentation/platform/pki/migration) to move from the earlier project-based model.+</Warning>-<br />+## Get started-<div style={{ position: "relative", paddingBottom: "56.25%", height: 0, overflow: "hidden", maxWidth: "100%" }}>- <iframe- src="https://www.youtube.com/embed/jP-9Ak0tr8A"- title="YouTube video player"- style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%", border: 0 }}- allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"- allowfullscreen- ></iframe>-</div>+Issue a certificate or sign an artifact, then learn how the parts of Certificate Manager fit together:-<br />+<CardGroup cols={2}>+ <Card title="Issue first certificate" icon="award" href="/documentation/platform/pki/quick-starts/issue-first-certificate">+ Issue a TLS certificate in under 10 minutes.+ </Card>+ <Card title="Sign first artifact" icon="file-pen" href="/documentation/platform/pki/quick-starts/sign-first-code">+ Sign a JAR file in under 10 minutes.+ </Card>+ <Card title="Concepts" icon="book-open" href="/documentation/platform/pki/concepts/certificate-lifecycle">+ Learn how Certificate Manager works.+ </Card>+</CardGroup>++## Certificate authorities++Set up the CAs that sign your certificates. To compare the two kinds, see [Certificate authorities](/documentation/platform/pki/ca/overview).<CardGroup cols={2}>- <Card title="Get Started" icon="rocket" href="/documentation/platform/pki/getting-started">- New to Certificate Manager? Start here to understand the core concepts and issue your first certificate.+ <Card title="Internal CA" icon="lock" href="/documentation/platform/pki/ca/private-ca">+ Create root and intermediate CAs in Infisical.+ </Card>+ <Card title="External CA" icon="landmark" href="/documentation/platform/pki/ca/external-ca">+ Issue from a public or enterprise CA, such as Let's Encrypt, DigiCert, AWS Private CA, or Microsoft ADCS.</Card>- <Card title="Reference Architecture" icon="network" href="/documentation/platform/pki/concepts/reference-architecture">- Planning a rollout? See a reference layout for running your PKI across teams and environments.+ <Card title="HSM connectors" icon="shield-half" href="/documentation/platform/pki/settings/hsm-connectors">+ Keep internal CA and signer keys in your own HSM.</Card></CardGroup>-## Core capabilities+## Managing certificates++Set the rules certificates must follow, then issue, deliver, and renew certificates for each service:<CardGroup cols={2}>- <Card title="Issue Certificates" icon="award" href="/documentation/platform/pki/applications/overview">- Issue X.509 certificates via API, ACME, EST, or SCEP for TLS, mTLS, and device authentication.+ <Card title="Applications" icon="layout-grid" href="/documentation/platform/pki/applications/overview">+ Give each service its own members, certificates, and settings.+ </Card>+ <Card title="Certificate policies" icon="shield-check" href="/documentation/platform/pki/settings/policies">+ Limit the subjects, names, key usages, algorithms, and validity a certificate can have.+ </Card>+ <Card title="Certificate profiles" icon="file-badge" href="/documentation/platform/pki/settings/profiles">+ Pair a policy with a CA for applications to issue from.+ </Card>+ <Card title="Enrollment methods" icon="log-in" href="/documentation/platform/pki/applications/enrollment-methods/overview">+ Request certificates through the API, ACME, EST, or SCEP, with guides for common tools.</Card>- <Card title="Sign Code" icon="file-pen" href="/documentation/platform/pki/code-signing/overview">- Sign software artifacts with centralized key management, approval workflows, and PKCS#11 integration.+ <Card title="Issue and manage certificates" icon="award" href="/documentation/platform/pki/applications/certificates">+ Issue, import, revoke, and export the certificates in an application.</Card>- <Card title="Discover Certificates" icon="radar" href="/documentation/platform/pki/discovery/overview">- Scan your infrastructure to find and inventory certificates you didn't know existed.+ <Card title="Approvals" icon="check-check" href="/documentation/platform/pki/applications/approvals">+ Require a review before a certificate is issued.</Card>- <Card title="Sync Certificates" icon="refresh-cw" href="/documentation/platform/pki/applications/certificate-syncs/overview">- Push certificates to AWS ACM, Azure Key Vault, Cloudflare, and other destinations.+ <Card title="Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/certificate-renewal">+ Renew a certificate, and change its details as part of the renewal.+ </Card>+ <Card title="Certificate syncs" icon="refresh-cw" href="/documentation/platform/pki/applications/certificate-syncs/overview">+ Push certificates to AWS, Azure, Cloudflare, load balancers, and servers.</Card></CardGroup>-## Lifecycle management+## Monitoring++Track every certificate in Certificate Manager, and find out about problems before they cause an outage:<CardGroup cols={2}>- <Card title="Auto-Renewal" icon="rotate-cw" href="/documentation/platform/pki/applications/enrollment-methods/overview">- Automate certificate renewal so nothing expires unexpectedly.+ <Card title="Certificate inventory" icon="list" href="/documentation/platform/pki/monitoring/certificate-inventory">+ Search, filter, and save views of every certificate.</Card>- <Card title="Alerting" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">- Get notified via Slack, PagerDuty, or webhooks when certificates expire or lifecycle events occur.+ <Card title="Discovery" icon="radar" href="/documentation/platform/pki/discovery/overview">+ Scan your network for certificates that Infisical didn't issue.</Card>- <Card title="Approval Workflows" icon="check-check" href="/documentation/platform/pki/applications/approvals">- Require human review before high-value certificates are issued.+ <Card title="Alerts" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">+ Get notified by email, Slack, PagerDuty, or webhook when certificates expire or change.</Card>- <Card title="Certificate Authorities" icon="landmark" href="/documentation/platform/pki/ca/overview">- Create private CA hierarchies or connect external CAs like DigiCert, Let's Encrypt, and AWS PCA.+ <Card title="Certificate cleanup" icon="trash-2" href="/documentation/platform/pki/settings/certificate-cleanup">+ Remove expired certificates automatically.</Card></CardGroup>+## Code signing++Sign software artifacts with keys kept in Infisical or in your own HSM, with approvals and an audit trail of every signature. To see how a signing operation works, see the [code signing overview](/documentation/platform/pki/code-signing/overview).++<CardGroup cols={2}>+ <Card title="Signers" icon="pen-tool" href="/documentation/platform/pki/code-signing/signers">+ Create signing identities and choose who can sign with each one.+ </Card>+ <Card title="Approvals" icon="check-check" href="/documentation/platform/pki/code-signing/approvals">+ Require approval before someone can sign with a signer.+ </Card>+ <Card title="Signing tools" icon="wrench" href="/documentation/platform/pki/guides/code-signing/jarsigner">+ Sign with jarsigner, apksigner, osslsigncode, cosign, OpenSSL, or GPG.+ </Card>+ <Card title="PKCS#11 module" icon="cpu" href="/documentation/platform/pki/code-signing/pkcs11-module">+ Connect standard signing tools to your signers.+ </Card>+ <Card title="Windows KSP" icon="windows" iconType="brands" href="/documentation/platform/pki/code-signing/windows-ksp">+ Sign Windows executables, DLLs, and MSIs with signtool.+ </Card>+</CardGroup>diff --git a/docs/documentation/platform/pki/quick-starts/issue-first-certificate.mdx b/docs/documentation/platform/pki/quick-starts/issue-first-certificate.mdxindex 00c927708b..0eaf7c6f78 100644--- a/docs/documentation/platform/pki/quick-starts/issue-first-certificate.mdx+++ b/docs/documentation/platform/pki/quick-starts/issue-first-certificate.mdx@@ -1,11 +1,15 @@---title: "Issue your first certificate"-sidebarTitle: "Issue certificate"+sidebarTitle: "Issue first certificate"description: "Issue a TLS certificate in under 10 minutes."---Issue a TLS certificate from your own private CA in about 10 minutes. You'll set up a certificate authority, create a policy and profile, then issue your first certificate.+<Tip>+ Visual learner? Watch an [introduction to certificate management with Infisical](https://www.youtube.com/watch?v=jP-9Ak0tr8A).+</Tip>+## Prerequisites- Product Admin permissions (to create CAs, policies, and profiles)diff --git a/docs/documentation/platform/pki/quick-starts/sign-first-code.mdx b/docs/documentation/platform/pki/quick-starts/sign-first-code.mdxindex 45b817f826..db3499521a 100644--- a/docs/documentation/platform/pki/quick-starts/sign-first-code.mdx+++ b/docs/documentation/platform/pki/quick-starts/sign-first-code.mdx@@ -1,6 +1,6 @@---title: "Sign your first artifact"-sidebarTitle: "Sign artifact"+sidebarTitle: "Sign first artifact"description: "Sign a JAR file using Infisical Code Signing in under 10 minutes."---diff --git a/docs/documentation/platform/pki/reference/infisical-agent.mdx b/docs/documentation/platform/pki/reference/infisical-agent.mdxindex aaaae8de70..760ec951d7 100644--- a/docs/documentation/platform/pki/reference/infisical-agent.mdx+++ b/docs/documentation/platform/pki/reference/infisical-agent.mdx@@ -1,6 +1,6 @@---title: "Infisical Agent reference"-sidebarTitle: "Infisical Agent"+sidebarTitle: "Infisical Agent reference"description: "Configuration reference for the Infisical Agent's certificate management mode."---diff --git a/docs/documentation/platform/pki/settings/alerts.mdx b/docs/documentation/platform/pki/settings/alerts.mdxdeleted file mode 100644index d040cb07d8..0000000000--- a/docs/documentation/platform/pki/settings/alerts.mdx+++ /dev/null@@ -1,182 +0,0 @@-----title: "Alerts"-sidebarTitle: "Alerts"-description: "Get notified about certificate events anywhere in Certificate Manager, inside or outside an application."------An alert under **Settings** > **Alerts** covers certificates across Certificate Manager for one event, whether or not they belong to an [Application](/documentation/platform/pki/applications/overview). Without filters, it covers every certificate. To alert on a single application, create an [application alert](/documentation/platform/pki/applications/alerting/overview) instead.--Certificate Manager alerts use the same events and [notification channels](/documentation/platform/pki/applications/alerting/overview#notification-channels) as application alerts. They can also alert on [signer certificate expiration](#signer-certificate-expiration) for **Code Signing**.--## Prerequisites--- The Certificate Manager **Admin** role to create or edit an alert-- For Slack, PagerDuty, and webhook channels, the Enterprise plan. Email channels are available on every plan.-- For email alerts, recipients who are organization members, or addresses on one of your organization's [verified email domains](/documentation/platform/email-domain)--## Create an alert--<Steps>- <Step>- Go to **Certificate Manager** > **Settings** and select the **Alerts** tab.- </Step>- <Step>- Select **Create Alert**.- </Step>- <Step>- Select the **Alert Type** from the **Certificate Lifecycle** or **Code Signing** group, then enter an **Alert Name** and an optional **Description**. For an expiration alert, enter **Alert Before** as a number and a unit, for example `30d` or `2w`, up to 365 days. Turn on **Repeat daily until expiry** to get a reminder every day. See [how often expiration alerts repeat](/documentation/platform/pki/applications/alerting/overview#faq). Select **Continue**.- </Step>- <Step>- On the **Filters** step, optionally select **Add Filter** to narrow the alert by **Applications**, **Certificate Profiles**, or **Source**. See [which certificates an alert covers](#which-certificates-an-alert-covers). **Matched Certificates** lists the active certificates the alert covers. Select **Continue**.- </Step>- <Step>- Select **Add Channel** and choose where to send notifications. You can add up to 10 channels. Select **Continue**.- </Step>- <Step>- Check the summary on the **Review** step, then select **Create Alert**.- </Step>-</Steps>--## Which certificates an alert covers--If you don't add a filter, the alert covers every certificate in Certificate Manager. Each filter you add narrows the alert, and a certificate must match every filter:--| Filter | Certificates covered |-|--------|----------------------|-| **Applications** | Certificates in one of the selected applications |-| **Certificate Profiles** | Certificates issued from one of the selected profiles |-| **Source** | Certificates with one of the selected sources: **Managed** for certificates issued through Certificate Manager, **Imported**, or **Discovered** |--For example, a **Source** filter set to **Imported** covers every imported certificate, including ones outside any application or profile. Add an **Applications** filter as well, and the alert covers only the imported certificates in those applications.--You can select up to 100 applications and 100 profiles.--## Signer certificate expiration--A **Signer Certificate Expiration** alert, in the **Code Signing** group, warns you before the certificate a signer currently signs with expires. It covers every active signer under **Code Signing** > **Signers**, has no filters, and skips the **Filters** step. It works like a certificate expiration alert: set **Alert Before** and optionally **Repeat daily until expiry**.--Only each signer's current certificate counts. When you reissue a signer's certificate, the alert follows the new one and stops alerting on the one it replaced. Signers that are disabled, failed, or still pending aren't covered.--## FAQ--<AccordionGroup>- <Accordion title="What happens to an alert when I delete an application or profile it lists?">- The alert keeps the deleted application or profile in its list, and the deleted one matches no certificates. When you edit the alert, the **Filters** step shows it as **Unknown application** or **Unknown profile**, so you can remove it.- </Accordion>- <Accordion title="What do webhook receivers get from Certificate Manager alerts?">- The same [webhook payload format](/documentation/platform/pki/applications/alerting/webhook-alerts#webhook-payload-format) as application alerts. These examples show one alert of each type:-- <CodeGroup>- ```json Certificate alert- {- "specversion": "1.0",- "type": "com.infisical.cert-manager.certificate.revocation",- "source": "/alerts/453421e2-2e73-4700-92c8-60ccd3e7073e",- "id": "8360c717-097a-4592-a2b0-63c494c3b558",- "time": "2026-10-05T21:37:35.935Z",- "datacontenttype": "application/json",- "subject": "cert-manager.certificate.revocation",- "data": {- "alert": {- "id": "453421e2-2e73-4700-92c8-60ccd3e7073e",- "name": "prod-revocations",- "resourceType": "cert-manager"- },- "items": [- {- "id": "4f70e08e-ad7a-4f94-ac16-241126ab88ed",- "title": "api.example.com",- "summary": "Certificate 'api.example.com' was revoked in application 'payments-api'",- "severity": "warning",- "fields": [- { "label": "Serial Number", "value": "77c2b1368a7dd4a8442c61d51d20cbdb2060a1e5" },- { "label": "Profile", "value": "tls-server" },- { "label": "Application", "value": "payments-api" },- { "label": "Expires", "value": "November 4, 2026 at 09:37 PM UTC" },- { "label": "Revocation Reason", "value": "Unspecified" }- ],- "resource": {- "id": "4f70e08e-ad7a-4f94-ac16-241126ab88ed",- "serialNumber": "77c2b1368a7dd4a8442c61d51d20cbdb2060a1e5",- "commonName": "api.example.com",- "altNames": [],- "status": "revoked",- "notBefore": "2026-10-05T21:37:28.426Z",- "notAfter": "2026-11-04T21:37:28.426Z",- "revokedAt": "2026-10-05T21:37:30.299Z",- "revocationReason": 0,- "profileId": "8d04ef1b-67cd-4021-8da4-b3096d11133b",- "profileName": "tls-server",- "applicationId": "d6e7232b-ffa5-48bf-9133-4731c6d001a0",- "applicationName": "payments-api"- }- }- ],- "metadata": {- "totalItems": 1,- "viewUrl": "https://app.infisical.com/organizations/<org-id>/cert-manager/inventory"- }- }- }- ```-- ```json Signer certificate expiration- {- "specversion": "1.0",- "type": "com.infisical.cert-manager.signer.certificate.expiry",- "source": "/alerts/9b3c1d2e-5f6a-4b7c-8d9e-0f1a2b3c4d5e",- "id": "2c4e6a8b-1d3f-4a5c-9e7b-0d2f4a6c8e1b",- "time": "2026-10-05T00:05:00.000Z",- "datacontenttype": "application/json",- "subject": "cert-manager.signer.certificate.expiry",- "data": {- "alert": {- "id": "9b3c1d2e-5f6a-4b7c-8d9e-0f1a2b3c4d5e",- "name": "signer-expiry",- "resourceType": "cert-manager.signer"- },- "items": [- {- "id": "7e1f3a5c-9b2d-4e6f-8a0c-1d3e5f7a9b2c",- "title": "release signing",- "summary": "Certificate 'release signing' of signer 'release-signer' expires on October 25, 2026 at 12:00 AM UTC",- "severity": "warning",- "fields": [- { "label": "Signer", "value": "release-signer" },- { "label": "Serial Number", "value": "0a1b2c3d4e5f60718293a4b5c6d7e8f901234567" },- { "label": "Expires", "value": "October 25, 2026 at 12:00 AM UTC" }- ],- "resource": {- "id": "7e1f3a5c-9b2d-4e6f-8a0c-1d3e5f7a9b2c",- "serialNumber": "0a1b2c3d4e5f60718293a4b5c6d7e8f901234567",- "commonName": "release signing",- "altNames": [],- "status": "active",- "notBefore": "2025-10-25T00:00:00.000Z",- "notAfter": "2026-10-25T00:00:00.000Z",- "signerIds": ["3d5f7a9b-2c4e-4f6a-8b0d-1e3f5a7c9e2b"],- "signerNames": ["release-signer"]- }- }- ],- "metadata": {- "totalItems": 1,- "viewUrl": "https://app.infisical.com/organizations/<org-id>/cert-manager/code-signing"- }- }- }- ```- </CodeGroup>- </Accordion>-</AccordionGroup>--## What's next?--<CardGroup cols={2}>- <Card title="Application alerts" icon="bell" href="/documentation/platform/pki/applications/alerting/overview">- Alert on the certificates in one application.- </Card>- <Card title="Webhook" icon="webhook" href="/documentation/platform/pki/applications/alerting/webhook-alerts">- Send alerts to your own endpoint.- </Card>-</CardGroup>diff --git a/docs/snippets/documentation/platform/pki/applications/alerting/start-alert.mdx b/docs/snippets/documentation/platform/pki/applications/alerting/start-alert.mdxnew file mode 100644index 0000000000..f17d1b7b44--- /dev/null+++ b/docs/snippets/documentation/platform/pki/applications/alerting/start-alert.mdx@@ -0,0 +1,54 @@+<Tabs>+ <Tab title="Certificate Manager">+ <Steps>+ <Step>+ Go to **Certificate Manager** > **Settings** and select the **Alerts** tab, then select **Create Alert**.+ </Step>+ <Step>+ Select the **Alert Type** from the **Certificate Lifecycle** or **Code Signing** group, then enter an **Alert Name** and an optional **Description**.+ </Step>+ <Step>+ For an expiration alert, enter **Alert Before** as a number and a unit. For example: `30d` or `2w`, up to 365 days.++ <Note>+ To get a reminder every day, turn on **Repeat daily until expiry**. Otherwise, the alert repeats on a [schedule based on **Alert Before**](/documentation/platform/pki/applications/alerting/overview#how-often-expiration-alerts-repeat).+ </Note>++ Select **Continue**.+ </Step>+ <Step>+ On the **Filters** step, optionally select **Add Filter** to [narrow the certificates the alert covers](/documentation/platform/pki/applications/alerting/overview#filter-a-certificate-manager-alert). A signer certificate expiration alert skips this step.++ Select **Continue** to go to the **Channels** step.+ </Step>+ </Steps>+ </Tab>+ <Tab title="Application">+ <Steps>+ <Step>+ Go to **Certificate Manager** > **Applications** and select your application.+ </Step>+ <Step>+ Select the **Settings** tab, then select **Create Alert** in the **Alerts** section.+ </Step>+ <Step>+ Select the **Alert Type**, then enter an **Alert Name** and an optional **Description**.+ </Step>+ <Step>+ For an expiration alert, enter **Alert Before** as a number and a unit. For example: `30d` or `2w`, up to 365 days.++ <Note>+ To get a reminder every day, turn on **Repeat daily until expiry**. Otherwise, the alert repeats on a [schedule based on **Alert Before**](/documentation/platform/pki/applications/alerting/overview#how-often-expiration-alerts-repeat).+ </Note>++ Select **Continue** to go to the **Channels** step.+ </Step>+ </Steps>++ An application can have one alert for each event. To notify more places about the same event, add more channels to that alert.+ </Tab>+</Tabs>++<Tip>+To add this channel to an existing alert instead, edit the alert and go to its **Channels** step.+</Tip>diff --git a/frontend/src/pages/cert-manager/pki-docs-urls.ts b/frontend/src/pages/cert-manager/pki-docs-urls.tsindex 026bf2b13b..93146bf4a3 100644--- a/frontend/src/pages/cert-manager/pki-docs-urls.ts+++ b/frontend/src/pages/cert-manager/pki-docs-urls.ts@@ -12,7 +12,7 @@ export const PkiDocsUrls = {// Overviewoverview: `${PKI_DOCS_BASE_URL}/overview`,- gettingStarted: `${PKI_DOCS_BASE_URL}/getting-started`,+ gettingStarted: `${PKI_DOCS_BASE_URL}/overview`,migration: `${PKI_DOCS_BASE_URL}/migration`,// Quick starts@@ -31,7 +31,7 @@ export const PkiDocsUrls = {policies: `${PKI_DOCS_BASE_URL}/settings/policies`,profiles: `${PKI_DOCS_BASE_URL}/settings/profiles`,certificateCleanup: `${PKI_DOCS_BASE_URL}/settings/certificate-cleanup`,- alerts: `${PKI_DOCS_BASE_URL}/settings/alerts`,+ alerts: `${PKI_DOCS_BASE_URL}/applications/alerting/overview`,hsmConnectors: `${PKI_DOCS_BASE_URL}/settings/hsm-connectors`},