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
Doc improvements
Carlos Monastyrskifb9c62ab169f
diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/linux-server.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/linux-server.mdxindex 9bc675cc83..f808cb234e 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/linux-server.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/linux-server.mdx@@ -35,7 +35,7 @@ Deploy certificates from Infisical to a directory on a Linux server over SSH. Fi- **Destination Directory**: The absolute path to the directory where certificate files are written, for example `/etc/ssl/certs`.4. Configure the **Target Host**. This step appears only when the connection is an LDAP Connection, because that connection reaches a whole domain rather than one machine:- - **Target Host**: The machine this sync delivers to. Servers found in the directory are offered as suggestions, and you can enter a host that is not listed. Enter a host name or an IPv4 address. Underscores, ports and IPv6 literals are not accepted.+ - **Target Host**: The machine this sync delivers to. Servers found in the directory are offered as suggestions, and you can enter a host that isn't listed. Enter a host name or an IPv4 address. Underscores, ports and IPv6 literals aren't accepted.- **Port**: Leave empty to use 22. Set a value only if the SSH listener is on a non-standard port.- **Trusted Host Keys**: Optional. Paste the output of `ssh-keyscan <host>`. When set, the sync only connects if the host presents one of these keys.@@ -103,11 +103,11 @@ Deploy certificates from Infisical to a directory on a Linux server over SSH. FiAn SSH Connection stores the target machine's address alongside its credential, so it reaches exactly one server. Pushing one certificate to fifty servers means fifty connections holding the same credential, and fifty objects to update when that credential is rotated.-An LDAP Connection removes that duplication. It is both the credential and the directory, so one connection serves as many syncs as you have servers. Each sync names its own **Target Host**, and every sync shares the one credential. When you rotate the service account's password on the connection, every sync that uses it picks up the new password on its next run with no further action.+An LDAP Connection removes that duplication. It's both the credential and the directory, so one connection serves as many syncs as you have servers. Each sync names its own **Target Host**, and every sync shares the one credential. When you rotate the service account's password on the connection, every sync that uses it picks up the new password on its next run with no further action.This works because an Active Directory service account is a single identity. On a domain-joined Linux host, the same username and password that performs the LDAP bind performs the SSH logon, so no second credential is needed. The host must accept domain credentials over SSH, which is what a directory client such as SSSD provides.-The **Target Host** field offers machines read from the directory. The list is not closed, because the name a domain controller advertises is not always the address you can reach, so you can enter a host that is not listed. The value must be a host name or an IPv4 address.+The **Target Host** field offers machines read from the directory. The list isn't closed, because the name a domain controller advertises isn't always the address you can reach, so you can enter a host that isn't listed. The value must be a host name or an IPv4 address.<Note>The sync authenticates to the Target Host with the connection's credential. Application Admins can set it, so give the service account only the access it needs to deliver certificates.diff --git a/docs/documentation/platform/pki/applications/certificate-syncs/windows-server.mdx b/docs/documentation/platform/pki/applications/certificate-syncs/windows-server.mdxindex f25605151e..676fd79f11 100644--- a/docs/documentation/platform/pki/applications/certificate-syncs/windows-server.mdx+++ b/docs/documentation/platform/pki/applications/certificate-syncs/windows-server.mdx@@ -38,7 +38,7 @@ Deploy certificates from Infisical to a directory on a Windows server over WinRM- **Destination Directory**: The absolute Windows drive path where certificate files are written, for example `C:\certs`. It is created if it does not exist. The path cannot contain `..` segments or consecutive separators.4. Configure the **Target Host**. This step appears only when the connection is an LDAP Connection, because that connection reaches a whole domain rather than one machine. A Windows (WinRM) Connection carries all of these itself:- - **Target Host**: The machine this sync delivers to. Servers found in the directory are offered as suggestions, and you can enter a host that is not listed. Enter a host name or an IPv4 address. Underscores, ports and IPv6 literals are not accepted.+ - **Target Host**: The machine this sync delivers to. Servers found in the directory are offered as suggestions, and you can enter a host that isn't listed. Enter a host name or an IPv4 address. Underscores, ports and IPv6 literals aren't accepted.- **Port**: Leave empty to use 5985, or 5986 when **Enable SSL** is on. Set a value only if the WinRM listener is on a non-standard port.- **Enable SSL**: Connect over HTTPS. When off, HTTP with NTLM message encryption is used and no server certificate is required.- **SSL Certificate**: Leave empty to verify against the system trust store, or paste the listener's certificate to verify a self-signed WinRM HTTPS listener.@@ -113,13 +113,13 @@ Deploy certificates from Infisical to a directory on a Windows server over WinRMA Windows (WinRM) Connection stores the target machine's address alongside its credential, so it reaches exactly one server. Pushing one certificate to fifty servers means fifty connections holding the same credential, and fifty objects to update when that credential is rotated.-An LDAP Connection removes that duplication. It is both the credential and the directory, so one connection serves as many syncs as you have servers. Each sync names its own **Target Host**, and every sync shares the one credential. When you rotate the service account's password on the connection, every sync that uses it picks up the new password on its next run with no further action.+An LDAP Connection removes that duplication. It's both the credential and the directory, so one connection serves as many syncs as you have servers. Each sync names its own **Target Host**, and every sync shares the one credential. When you rotate the service account's password on the connection, every sync that uses it picks up the new password on its next run with no further action.This works because an Active Directory service account is a single identity. The same username and password that performs the LDAP bind performs the WinRM logon, so no second credential is needed.Infisical derives that logon name rather than asking for it twice. It reads the domain's NetBIOS name from the directory and signs in as `NETBIOS\account`, for example `CORP\svc-certs`. The account part comes from the connection's bind identity: from the name before the `@` when the bind is a user principal name, and read from the directory as the account's `sAMAccountName` when the bind is a distinguished name. Grant WinRM rights to that account, not to the connection's bind string.-The **Target Host** field offers servers read from the directory. The list is not closed, because the name a domain controller advertises is not always the address you can reach, so you can enter a host that is not listed. The value must be a host name or an IPv4 address.+The **Target Host** field offers servers read from the directory. The list isn't closed, because the name a domain controller advertises isn't always the address you can reach, so you can enter a host that isn't listed. The value must be a host name or an IPv4 address.<Note>The sync authenticates to the Target Host with the connection's credential. Application Admins can set it, so give the service account only the access it needs to deliver certificates.