Skip to content

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

chore(pki): share imperva api descriptions and list the application prerequisite

bernie-g986ee5257e50
diff --git a/backend/src/lib/api-docs/constants.ts b/backend/src/lib/api-docs/constants.ts
index 925928fe5d..54f9efc716 100644
--- a/backend/src/lib/api-docs/constants.ts
+++ b/backend/src/lib/api-docs/constants.ts
@@ -4718,6 +4718,11 @@ export const AGENT_VAULT = {
}
};
+export const IMPERVA_PKI_SYNC_DESTINATION_CONFIG = {
+ siteId: "The numeric ID of the Imperva website that receives the certificate.",
+ siteName: "The website's name, kept for display. Imperva's website ID is what the sync acts on."
+};
+
export const PALO_ALTO_NETWORKS_PKI_SYNC_DESTINATION_CONFIG = {
template:
"The Panorama template to store certificates in. Required when the connection points to a Panorama, and not allowed for a firewall.",
diff --git a/backend/src/services/pki-sync/imperva/imperva-pki-sync-schemas.ts b/backend/src/services/pki-sync/imperva/imperva-pki-sync-schemas.ts
index 91f9f63836..9db0e802e0 100644
--- a/backend/src/services/pki-sync/imperva/imperva-pki-sync-schemas.ts
+++ b/backend/src/services/pki-sync/imperva/imperva-pki-sync-schemas.ts
@@ -1,6 +1,7 @@
import RE2 from "re2";
import { z } from "zod";
+import { IMPERVA_PKI_SYNC_DESTINATION_CONFIG } from "@app/lib/api-docs";
import { openApiHidden } from "@app/server/lib/schemas";
import { AppConnection } from "@app/services/app-connection/app-connection-enums";
import { pkiDescriptionSchema } from "@app/services/certificate-common/certificate-constants";
@@ -23,13 +24,13 @@ export const ImpervaPkiSyncConfigSchema = z.object({
.refine((val) => SITE_ID_PATTERN.test(val), {
message: "Site ID must be the numeric Imperva website ID"
})
- .describe("The numeric ID of the Imperva website that receives the certificate."),
+ .describe(IMPERVA_PKI_SYNC_DESTINATION_CONFIG.siteId),
siteName: z
.string()
.trim()
.max(512, "Site name cannot exceed 512 characters")
.optional()
- .describe("The website's name, kept for display. Imperva's website ID is what the sync acts on.")
+ .describe(IMPERVA_PKI_SYNC_DESTINATION_CONFIG.siteName)
});
export const ImpervaPkiSyncOptionsSchema = BasePkiSyncOptionsSchema.pick({
diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/imperva.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/imperva.mdx
index c9622a3e0b..cf130a841e 100644
--- a/docs/documentation/platform/pki/applications/certificate-syncs/imperva.mdx
+++ b/docs/documentation/platform/pki/applications/certificate-syncs/imperva.mdx
@@ -18,6 +18,7 @@ Imperva stores one custom certificate per website for each key type, so a sync t
## Prerequisites
+- An [Application](/documentation/platform/pki/applications/overview) holding the certificate you want to sync
- An [Imperva Connection](/integrations/app-connections/imperva) whose API key has the **Manage SSL Certificates** permission
- A website already protected by Imperva Cloud WAF
- A certificate whose subject alternative names cover every managed domain on that website