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 ...
    • "[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 ...
    • Jobs not returning correctly from Get-PSUJob

      Version: 1.5 Issue: When running Get-PSUJob and passing in a script returned from Get-PSUScript, jobs may not be returned correctly.  Get-PSUScript -Name 'Script.ps1' | Get-PSUJob  Root Cause: If the Universal 1.4 PowerShell module is installed, and ...
    • ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY when accessing PowerShell Universal

      Version: ​Any Issue: When accessing PowerShell Universal with a Chromium-based browser such as Google Chrome or Microsoft Edge, you can encounter an error when HTTPS is enabled. The error will state ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY.  Root ...