PowerShell Remoting Protocol (PSRP)

Upgrade your production inventories from legacy WinRM to PSRP to eliminate performance bottlenecks. By switching to PSRP and enforcing certificate validation, you get faster, secure remote management using persistent runspaces over your existing network.

Production PSRP inventory configuration

[windows]
winserver.example.com ansible_host=192.168.1.10

[windows:vars]
ansible_user=AnsibleUser@EXAMPLE.COM
ansible_password={{ vault_win_password }}
ansible_connection=psrp
ansible_psrp_port=5986
ansible_psrp_auth=kerberos
ansible_psrp_kerberos_delegation=true
ansible_psrp_cert_validation=validate
ansible_psrp_ca_cert=/etc/pki/ca-trust/source/anchors/internal_corporate_ca.pem

Security Best Practice: Never use ansible_psrp_cert_validation: ignore in production HTTPS environments. Only bypass validation in isolated lab spaces or when executing over HTTP (Port 5985) with message-level encryption strictly enabled (ansible_psrp_message_encryption: always). When Kerberos authentication is combined with message encryption over HTTP, traffic is secured at the protocol layer, making transport-level TLS validation optional.