New-WebServiceProxy needs Force parameter to ignore SSL errors - by HalR

Status : 

 


56
0
Sign in
to vote
ID 419466 Comments
Status Active Workarounds
Type Suggestion Repros 3
Opened 2/28/2009 6:20:38 AM
Access Restriction Public

Description

In a lab environment, or a low-budget situation, SSL certificates come last on the todo list.  Currently, the New-WebServiceProxy cmdlet cannot be used with self-signed certificates. When you control the network, self-signed certs present little to no risk and are very commonly used.  Please add a Force parameter (or similar) to this cmdlet to allow for ignoring acceptable SSL cert exceptions.
Sign in to post a comment.
Posted by 4cbmelin on 3/21/2017 at 10:16 AM
A workaround we are using is to add the following line before we create the Web Service Proxy:
[System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}
Posted by brianary on 3/17/2015 at 10:42 AM
A "ForceDirect" param to disable the system proxy could also help.
Posted by Dodge on 12/30/2014 at 1:47 PM
Same problem here... still occurring apparently... no force available.
Posted by Joel 'Jaykul' Bennett on 11/3/2011 at 7:33 PM
The new Invoke-RestMethod and Invoke-WebRequest need this too!
Posted by Joel Bennett on 2/28/2009 at 2:37 PM
Can this be solved by just (pre) trusting the SSL cert? That is, adding the SSL cert to your Trusted group?