You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been testing with the latest version you've released, and am seeing the following error when using a certificate thumbprint:
The WinRM client cannot process the request. The certificate CN and the hostname that were provided do not match.
I am using the following configuration:
Ensure = "Present"
Transport = "HTTPS"
CertificateThumbprint = "$thumbprinthere"
I believe this is because I cannot specify (and write) the HostName parameter that the WinRM client demands. If we could add the hostname parameter to be able to write, I believe that would solve my use case.
We're able to bind the certificate to a WSMan listener with the following command:
New-WSManInstance winrm/config/Listener -SelectorSet @{ Address="*";Transport="HTTPS"} -ValueSet @{Hostname="devOps";CertificateThumbprint=$thumbprint}
It's certainly a bit unorthodox, but it fits our use case.
Let me know if I can help any further- thank you for supporting this!
The text was updated successfully, but these errors were encountered:
From Issue #8 raised by @ttdgcp:
I've been testing with the latest version you've released, and am seeing the following error when using a certificate thumbprint:
The WinRM client cannot process the request. The certificate CN and the hostname that were provided do not match.
I am using the following configuration:
Ensure = "Present"
Transport = "HTTPS"
CertificateThumbprint = "$thumbprinthere"
I believe this is because I cannot specify (and write) the HostName parameter that the WinRM client demands. If we could add the hostname parameter to be able to write, I believe that would solve my use case.
We're able to bind the certificate to a WSMan listener with the following command:
New-WSManInstance winrm/config/Listener -SelectorSet @{ Address="*";Transport="HTTPS"} -ValueSet @{Hostname="devOps";CertificateThumbprint=$thumbprint}
It's certainly a bit unorthodox, but it fits our use case.
Let me know if I can help any further- thank you for supporting this!
The text was updated successfully, but these errors were encountered: