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
fix(pki): rename truststore toggle to include truststore
bernie-g2d101b9f2bf4
diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/linux-server.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/linux-server.mdxindex 94044c49ca..dca9687b3c 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/linux-server.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/linux-server.mdx@@ -47,7 +47,7 @@ Deploy certificates from Infisical to a directory on a Linux server over SSH. Fi- **Owner** and **Group**: Optionally set the owner and group on the delivered files. Changing ownership requires the connection user to be root or to have passwordless sudo.- **PKCS#12 Password** or **JKS Password**: Required when the export format is PKCS#12 or Java KeyStore. It protects the delivered bundle or keystore.- **Keystore Alias**: For PKCS#12 and Java KeyStore, the alias of the private key entry, such as the value Tomcat expects in `certificateKeyAlias`. Leave it empty to use the base file name from the certificate name schema.- - **Deliver Truststore**: For Java KeyStore, also write a `.truststore.jks` file that holds the issuing CAs and the root CA as trusted certificates. It uses the same password as the keystore.+ - **Include Truststore**: For Java KeyStore, also write a `.truststore.jks` file that holds the issuing CAs and the root CA as trusted certificates. It uses the same password as the keystore.- **Include Private Key**: For PEM, controls whether the private key is written alongside the certificate. The sync fails for a certificate whose key is not available, for example one issued from an external CSR.- **Include Root CA in Certificate Chain**: Include the root CA in the delivered chain. Leave it off when the consuming service only needs the intermediates.- **Enable Removal of Certificates**: Delete the delivered files from the server when a certificate is removed from the sync, revoked, or expired.@@ -144,7 +144,7 @@ The file extension is set by the export format, not by the name schema. The name**PKCS#12** writes a single password-protected `.pfx` bundle that contains the certificate, chain, and private key.-**Java KeyStore** writes a password-protected `.jks` keystore for Java servers such as Tomcat, WebLogic, and JBoss. The keystore holds one private key entry with the certificate, chain, and private key, and the key uses the same password as the keystore. If you turn on **Deliver Truststore**, the sync also writes a `.truststore.jks` file with each issuing CA and the root CA as trusted certificates. The truststore includes the root CA even when **Include Root CA in Certificate Chain** is off, and it never includes the certificate itself.+**Java KeyStore** writes a password-protected `.jks` keystore for Java servers such as Tomcat, WebLogic, and JBoss. The keystore holds one private key entry with the certificate, chain, and private key, and the key uses the same password as the keystore. If you turn on **Include Truststore**, the sync also writes a `.truststore.jks` file with each issuing CA and the root CA as trusted certificates. The truststore includes the root CA even when **Include Root CA in Certificate Chain** is off, and it never includes the certificate itself.Infisical writes a new keystore on every sync instead of adding to the file on the host. After a renewal, the keystore holds only the new certificate under the same alias, so old entries don't build up. Point your Java server at a keystore that only this sync writes to, because anything else in that file is replaced on the next sync.diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/windows-server.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/windows-server.mdxindex 2d3fcd30f8..22542e11a3 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/windows-server.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/windows-server.mdx@@ -55,7 +55,7 @@ Deploy certificates from Infisical to a directory on a Windows server over WinRM- **File Permissions**: Optionally grant Windows users or groups (for example a service account) Read, Modify, or Full Control on the delivered files, so you can restrict who reads the private key. Rules are added on top of the destination folder's inherited permissions.- **PKCS#12 Password** or **JKS Password**: Required when the export format is PKCS#12 or Java KeyStore. It protects the delivered bundle or keystore.- **Keystore Alias**: For PKCS#12 and Java KeyStore, the alias of the private key entry, such as the value Tomcat expects in `certificateKeyAlias`. Leave it empty to use the base file name from the certificate name schema.- - **Deliver Truststore**: For Java KeyStore, also write a `.truststore.jks` file that holds the issuing CAs and the root CA as trusted certificates. It uses the same password as the keystore.+ - **Include Truststore**: For Java KeyStore, also write a `.truststore.jks` file that holds the issuing CAs and the root CA as trusted certificates. It uses the same password as the keystore.- **Include Private Key**: For PEM, controls whether the private key is written alongside the certificate. The sync fails for a certificate whose key is not available, for example one issued from an external CSR.- **Include Root CA in Certificate Chain**: Include the root CA in the delivered chain. Leave it off when the consuming service only needs the intermediates.- **Enable Removal of Certificates**: Delete the delivered files from the server when a certificate is removed from the sync, revoked, or expired.@@ -153,7 +153,7 @@ The file extension is set by the export format, not by the name schema. The name**PEM** writes the certificate, chain, and private key (when included) as separate files. The certificate and chain files use the extension you select, either `.pem` (default) or `.crt`.-**Java KeyStore** writes a password-protected `.jks` keystore for Java servers such as Tomcat, WebLogic, and JBoss. The keystore holds one private key entry with the certificate, chain, and private key, and the key uses the same password as the keystore. If you turn on **Deliver Truststore**, the sync also writes a `.truststore.jks` file with each issuing CA and the root CA as trusted certificates. The truststore includes the root CA even when **Include Root CA in Certificate Chain** is off, and it never includes the certificate itself.+**Java KeyStore** writes a password-protected `.jks` keystore for Java servers such as Tomcat, WebLogic, and JBoss. The keystore holds one private key entry with the certificate, chain, and private key, and the key uses the same password as the keystore. If you turn on **Include Truststore**, the sync also writes a `.truststore.jks` file with each issuing CA and the root CA as trusted certificates. The truststore includes the root CA even when **Include Root CA in Certificate Chain** is off, and it never includes the certificate itself.Infisical writes a new keystore on every sync instead of adding to the file on the host. After a renewal, the keystore holds only the new certificate under the same alias, so old entries don't build up. Point your Java server at a keystore that only this sync writes to, because anything else in that file is replaced on the next sync.diff --git a/frontend/src/components/pki-syncs/forms/PkiSyncOptionsFields/ServerExportFormatFields.tsx b/frontend/src/components/pki-syncs/forms/PkiSyncOptionsFields/ServerExportFormatFields.tsxindex 462460c618..b95c79e8e7 100644--- a/frontend/src/components/pki-syncs/forms/PkiSyncOptionsFields/ServerExportFormatFields.tsx+++ b/frontend/src/components/pki-syncs/forms/PkiSyncOptionsFields/ServerExportFormatFields.tsx@@ -210,7 +210,7 @@ export const ServerExportFormatFields = ({ isUpdate }: Props) => {<Field className="mb-4"><Field orientation="horizontal"><FieldContent>- <Label htmlFor="include-truststore">Deliver truststore</Label>+ <Label htmlFor="include-truststore">Include truststore</Label><FieldDescription>When enabled, a separate .truststore.jks file holding the certificate's CAchain and root CA as trusted entries is written next to the keystore. It usesdiff --git a/frontend/src/helpers/pkiSyncs.ts b/frontend/src/helpers/pkiSyncs.tsindex cc3059db15..09ec299648 100644--- a/frontend/src/helpers/pkiSyncs.ts+++ b/frontend/src/helpers/pkiSyncs.ts@@ -153,7 +153,7 @@ export const BOOLEAN_SYNC_OPTION_FIELDS = [{ key: "preserveItemOnRenewal", label: "Preserve Item on Renewal" },{ key: "updateExistingCertificates", label: "Update Existing Certificates" },{ key: "combineCertificateChain", label: "Combine Certificate and Chain" },- { key: "includeTruststore", label: "Deliver Truststore" },+ { key: "includeTruststore", label: "Include Truststore" },{ key: "includePrivateKey", label: "Include Private Key" }] as const;