Invoke webrequest удаленный сервер возвратил ошибку 401 несанкционированный

I’m attempting to POST a SOAP message to an Apache web server (Cisco Call Manager) using either the WebClient component of Powershell or the Invoke-WebRequest command. When using either function, I continue to get a «401 Unauthorized» response.
The server requires Basic Base64 encoded authentication. 

I can successfully post my content using SoapUI or cURL, however I would love to build this in Powershell. I’ve monitored the HTTP headers during the post in both Fiddler and SoapUI logs. 

When browsing to the URL i need to send the post too, I am prompted for authentication, after providing the authentication, I connect to the page and can POST my data. Based on that behavior and how the responses are being returned in Fiddler, it looks like
my Powershell command using either WebClient or Invoke-Webrequest, is send the request, however the server is responding with a 401 unauthorized and not trying to pass the credentials when it receives that response.

What I haven’t been able to figure out, is how to keep that session alive so that when the server sends back 401 and prompts for credentials, I can actually pass the credentials back and complete my POST.

Can anyone help out here and provide some sample code on how to accomplish this? Thanks.

Dear community, 

I’m having trouble connecting to my companies Jira server using a powershell script and the Invoke-WebRequest commandlet.

I’m using the following script. Note that I’m getting the same error with any valid URI to this Jira server. While the same user can access all these URI’s through a webbrowser just fine.

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$baseUrl = "https://MyDomain.atlassian.net"
$jql = "%22Epic Link%22 = SD-2"
$user = 'USER@MyDomain.com'
$pass = 'TheCorrectPassword'
$pair = "$($user):$($pass)"
$encodedCreds = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes($pair))
$basicAuthValue = "Basic $encodedCreds"
$authHeader = @{
Authorization = $basicAuthValue
}
Invoke-WebRequest -uri $($baseUrl + "/rest/api/latest/search?jql=$jql") -Headers $authHeader -UseBasicParsing -ErrorAction Stop -Verbose

Output from powershell:

Invoke-WebRequest : The remote server returned an error: (401) Unauthorized.
At D:WorkJiraAccess2.ps1:22 char:1
+ Invoke-WebRequest -uri $($baseUrl + "/rest/api/latest/search?jql=$jql ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
eption
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Если при get-запросе через Powershell и Invoke-Webrequest появляется ошибка «The remote server returned an error: (401) Unauthorized.», то необходимо использовать -UseDefaultCredentials.
В моем случае и это не помогло, сервер отвечал на запрос: данный браузер или операционная система не поддерживается. Помогло притвориться InternetExplorer через подмену UserAgent:

Invoke-WebRequest -Uri «http://site»-UseDefaultCredentials —UserAgent([Microsoft.PowerShell.Commands.PSUserAgent]::InternetExplorer)

I made a Stack Overflow post about this here.

I’m trying to integrate Sage 50 Accounts Professional V23 with my external application through SData. So far I’ve tried connecting, with the SData address I got through Tools > Internet Options > SData Settings, but when I make the GET request using the credentials I used to sign in to Sage 50, I get 401 unauthorized error.

Sage 50 is hosted on Windows Server 2012, I’ve tried using PowerShell to make the request and tried using the browser; both fail.

This is the PowerShell code I used:

$username = "MyUsername"
$password = ConvertTo-SecureString 'MyPassword' -AsPlainText -Force
$cred = new-object -typename System.Management.Automation.PSCredential -argumentlist $username, $password
Invoke-WebRequest -Credential $cred -Uri 'http://localhost:5493/sdata/accounts50/GCRM/{string-of-numbers-letters-and-dashes}/salesOrders'

When going to the same url through the browser, a browser window pops up asking for authentication. I provide it, then click login, after doing that the windows pops up again with empty username and password. No matter how many times I fill them out, I get the same thing. If I click «Cancel» instead of login, then I get a 401 unauthorized error

Такое поведение возникает из-за перенаправления; при выполнении этого дополнительного запроса к месту перенаправления заголовок авторизации не включается.

По этой причине PowerShell 6.0.0 добавил параметр PreserveAuthorizationOnRedirect.

Indicates the cmdlet should preserve the Authorization header, when present, across redirections.
By default, the cmdlet strips the Authorization header before redirecting. Specifying this parameter disables this logic for cases where the header needs to be sent to the redirection location.

Справка по Invoke-WebRequest

В качестве альтернатива, если вы не используете PowerShell 6, вы можете обойти его с помощью сценария более низкого уровня с использованием System.Net.WebRequest, который определяет свойство AllowAutoRedirect, которое может быть установлено на False, чтобы пропустить перенаправление после успешного POST, избегая ошибки 401 .

Обратите внимание, что вы должны сами позаботиться о таких вещах, как форматирование данных / тела (json, form-urlencoded, …) и http-заголовки.

Скрипт будет выглядеть так, как показано ниже.
Обратите внимание на строку с AllowAutoRedirect = $false.

$creds = "$($BASIC_AUTH_USER):$($BASIC_AUTH_PASS)"
$encodedCreds = [System.Convert]::ToBase64String([System.Text.Encoding]::ASCII.GetBytes($creds))
$basicAuthValue = "Basic $encodedCreds"

$url = "http://your.url"
$request = [System.Net.WebRequest]::CreateHttp($url);   
$request.Method = "post"
$request.Headers.Add("Authorization", $basicAuthValue)
$request.AllowAutoRedirect = $false

$body = "your formatted data goes here"
$bytes = [System.Text.Encoding]::UTF8.GetBytes($body);
$stream = $request.GetRequestStream()
$stream.Write($bytes, 0, $bytes.Length);
$stream.Close();

$request.GetResponse();