The purpose of this bug report is to highlight the lack of informative logging within the PSU logs during the below scenario which can happen by accident 🦧.
Setup Windows Authentication with PowerShell Universal (running under a local ActiveDirectory service account) and ensure the PSU application is working as expected for the audience.
Stop the PSU service on the PSU node.
Reconfigure the PSU service to use the local SYSTEM account instead of the service account that you configured in Step 1.
Restart the PSU service
Attempt to have a user access the PSU node from their web browser
Observe error 500 (shown below)
The description in the log is generic.
Expected behavior
An informative description and even suggestions could be written to the PSU logs when the PSU server receives an anonymous request between authentication handshake requests.
Actual behavior
A generic description is written to the PSU logs when the PSU server receives an anonymous request between authentication handshake requests.
Version
5.0.0-betaX
Severity
Low
Environment
msi
Steps to Reproduce
The purpose of this bug report is to highlight the lack of informative logging within the PSU logs during the below scenario which can happen by accident 🦧.
The description in the log is generic.
Expected behavior
Actual behavior
Additional Environment data
This error is covered in the PSU FAQ at https://support.ironmansoftware.com/portal/en/kb/articles/kb00018-an-anonymous-request-was-received-in-between-authentication-handshake-requests. This report is similar to #1684
Screenshots/Animations
No response