KB0018 - An anonymous request was received in between authentication handshake requests.

KB0018 - An anonymous request was received in between authentication handshake requests.

Symptom #1

PowerShell Universal returns a 500 error when visiting the website that is using Windows Authentication. 

Symptom #2

When viewing the log file in C:\ProgramData\PowerShellUniversal or within the admin console under Settings \ General \Diagnostics, there is an error message with the following content: An anonymous request was received in between authentication handshake requests.

Root Cause

The root cause of this issue is an invalid or unconfigured SPN for the machine running PowerShell Universal. 

Solution

Ensure that an SPN has been correctly created within your domain. An example command would look like: 
  1. setspn -S HTTP/myservername.mydomain.com myuser
You can view configured SPNs by using the following command. 
  1. setspn -l myservername.mydomain.com
For more information, read our documentation on Windows Authentication

    • Related Articles

    • "[WARN] Call failed. An error occurred while sending the request." message in all jobs

      Version: Any Root Cause When PowerShell Universal starts a new job, it uses the Management API to retrieve job information from the server. It does this over HTTP and will generate a Read-Only app token for the identity of the user that started or ...
    • KB0017 - Windows Auth Checklist

      Purpose The purpose of this article is to list the prerequisite conditions for ensuring that Windows Authentication in PowerShell Universal will function as expected (i.e. seamless logon without authentication pop-ups) Scope The scope of this article ...
    • KB0016 - Capturing a Network Trace in Chrome or Edge

      About Occasionally, Ironman Software support engineers will request more information while trying to diagnosis a problem that may be happening when access PowerShell Universal. Since PowerShell Universal is a web application, web application ...
    • KB0003 - Slow Endpoints and TLS Settings

      Be advised that if the TLS settings on a Windows Server are modified, this can result in a severe performance degradation Symptom #1 In the Event Viewer (System Log) there are errors with source Schannel indicating that a "fatal error that occurred ...
    • "Did not receive port from client process." when running jobs

      Version: Any Problem: When executing jobs, jobs can fail without starting the PowerShell script. Within the PowerShell Universal logs, you will see an error that states: Did not receive port from client process. Root Cause: When running in ...