PowerShell Invoke-RestMethod cmdlet failing to send second authentication challenge?

Asked Dec 07 '16 at 00:02

Active Jul 16 '19 at 19:32

Viewed 209 times

When using PowerShell's Invoke-RestMethod to a service that uses Windows Authentication, I'm getting a "401.2 Not Authorized" Exception, but I've confirmed via

$currentUser = [System.Security.Principal.WindowsIdentity]::GetCurrent().Name

that I'm using the expected user. I've verified that user is allowed in my service's web.config. Here's my actual invocation:

Invoke-RestService -Method "POST" -Uri $serviceApiUri -Body (ConvertTo-Json $body) -UseDefaultCredentials -ContentType "application/json"

Anyone else have issues with PowerShell's Invoke-RestMethod with Windows Authentication? How can I fix this?

edited Jul 16 '19 at 19:32

TylerH

20,799
66
75
101

asked Dec 07 '16 at 00:02

John

May I know the error you are getting? Or could you please post the screenshot? Its a very generic question to answer. – Ranadip Dutta Dec 07 '16 at 03:50
What version of Windows? – T-Heron Dec 07 '16 at 20:55

PowerShell Invoke-RestMethod cmdlet failing to send second authentication challenge?

0 Answers0