Setup
- Infisical UI
- API
Gather WinRM Details
You will need the following for the target Windows host:
- Host: The DNS name (FQDN) or IP address of the Windows host.
- Port: The WinRM port.
5985for HTTP with NTLM message encryption,5986for HTTPS. - Username: A Windows login, either
DOMAIN\useroruser@domain.com. - Password: The account password.
The account must be able to open a WinRM session and write to the destination directory used by the certificate sync. HTTP with NTLM message encryption works against the default WinRM listener with no extra setup. HTTPS additionally requires a WinRM HTTPS listener on the host.
Navigate to App Connections
In the Infisical dashboard, navigate to Organization Settings > App Connections and click Add Connection.
Fill in Connection Details
Fill in the connection form:
- Gateway: The Gateway that can reach the Windows host. This is required.
- Host and Port: The Windows host and WinRM port (5985 for HTTP, 5986 for HTTPS).
- Username and Password: The Windows account credentials.
- Enable SSL: Off (default) uses HTTP with NTLM message encryption, which needs no server certificate. On uses HTTPS.
- SSL Certificate (HTTPS only): Optional CA certificate (PEM). Leave empty to verify the listener against the system trust store, or paste the listener’s certificate to verify a self-signed WinRM HTTPS listener.
- Reject Unauthorized (HTTPS only): When on (default), Infisical only connects if the listener presents a valid, trusted certificate.
Connection Created
Your Windows (WinRM) Connection is now available for use with the Windows Server Certificate Sync.
Transport
By default (SSL disabled) the connection uses HTTP with NTLM message encryption on port 5985, which keeps the certificate and key confidential without a server certificate. This is the zero-configuration posture most Windows hosts already ship with. Enable SSL to use HTTPS on port 5986. For a self-signed HTTPS listener, paste its certificate as the SSL certificate so it can be authenticated. For a host on an untrusted network, prefer HTTPS.FAQ
Why does this connection require a Gateway?
Why does this connection require a Gateway?
The Gateway runs the WinRM session on Infisical’s behalf, so a Gateway with access to the Windows host is always required.