OpenID Connect does not work with HTTP
Problem: When configuring PowerShell Universal OpenID Connect authentication, the server will return a 500 error when attempting to authenticate.
Chrome 80 introduced new settings that require cross-site cookies to be secure. Although you can configure authentication provides like Azure Active Directory to support HTTP when using localhost, Chrome (and Chrome based browsers like Microsoft Edge) will prevent the HTTP cookie from being shared and thus throw an exception.
To work around this issue, you will need to display the security setting within the Chrome settings. Enter chrome://flags into the browser address bar and search for "Cookies without SameSite must be secure". Disable this setting and restart the browser.