OpenID Connect does not work with HTTP

OpenID Connect does not work with HTTP

Version: Any
Problem: When configuring PowerShell Universal OpenID Connect authentication, the server will return a 500 error when attempting to authenticate. 
Root Cause
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. 
Workaround
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. 
    • Related Articles

    • Out-String doesn't work in Universal Dashboard

      Product: PowerShell Universal - Any Version  Issue: Out-String does not appear to work in PowerShell Universal Dashboard running in Windows PowerShell v5.1. You will receive empty strings when attempting to use Out-String. See the example below for ...
    • IIS: HTTP Error 502.5 - ANCM Out-Of-Process Startup Failure

      Applies to: PowerShell Universal 1.4 or later When configuring PowerShell Universal to run under IIS, you may be presented with an error that states ANCM Out-Of-Process Startup Failure. This error can be presented for a variety of reasons but the ...
    • KB0002 - Security features of PowerShell Universal

      In terms of security features, PowerShell Universal currently provides: HTTPS for over the wire encryption Authentication providers such as SAML2, OpenID Connect, Windows (NTLM\Kerberos), WS-Federation, client certificate, and basic auth Role-based ...
    • KB0021 - Unable to update Dashboard Pages in PowerShell Universal 3.6.4

      Purpose Due to an issue with the client-side application in PowerShell Universal 3.6.4, you may experience a problem updating page content. When clicking the Save button, a toast message would be shown that states that a 400 HTTP error had occurred. ...
    • 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 ...