New-WebServiceProxy needs Force parameter to ignore SSL errors
Votes from Connect: 42
Original Date Submitted: 2/28/2009 10:20:55 PM
Site Name: PowerShell
Feedback ID: 419466
Frequency: Always Happens
Regression: Yes, this happens in all previous versions
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.
Product Studio item created by Connect Synchronizer due to creation of feedback ID 419466 (http://connect.microsoft.com/feedback/ViewFeedback.aspx?SiteID=99&FeedbackID=419466).
PS > $proxy = New-WebServiceProxy -Uri $Uri -Credential (Get-Credential)
cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
New-WebServiceProxy : The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Internal BugId: 1954