KB0022 - Unable to login after upgrading to PowerShell Universal 3.7.1

KB0022 - Unable to login after upgrading to PowerShell Universal 3.7.1

Affected Versions

- PowerShell Universal 3.7.0
- PowerShell Universal 3.7.1

Issue

A user attempts to login with the default admin account and cannot access the system. 

Solution

- Upgrade to PowerShell Universal 3.7.2
- Remove the admin account from the database (LiteDB or SQL) in the identities table
- Downgrade to 3.6.4

Root Cause

PowerShell Universal 3.7 added a local account feature to allow for users to create accounts directly within PowerShell Universal. The default admin account is considered a local account. If the system had previously been accessed by the admin account, and no other authentication or role configuration was completed and no license was installed, the user would not be able to login because the enterprise login features were either disabled due to licensing or unconfigured.

    • Related Articles

    • PowerShell Universal Service crashes on startup after an upgrade to 1.4.6

      Version: PowerShell Universal 1.4.6 Issue The PowerShell Universal service will crash with the following error in Event Viewer.  Application: Universal.Server.exe CoreCLR Version: 4.700.19.56402 .NET Core Version: 3.1.0 Description: The process was ...

    • PowerShell Universal crashes after upgrade to 1.5

      Version: 1.5 Issue: The PowerShell Universal service will not start properly when upgrading from 1.4 to 1.5. The following error is shown in the log.  Unhandled exception. System.InvalidCastException: Unable to cast object of type ...

    • KB0011 - Are licenses different between Production, QA and Test/Development servers?

      Update January 24th, 2023 Adam recently summarized the Developer's license per below: The only real limitation on the developer license is that it cannot be accessed remotely. The server is only available on loopback when using the dev license. If ...

    • KB0074 - Connecting to PSU API w/Windows Auth

      Scope This article applies only to PSU environments where Windows Authentication[1] is enabled and known to be working[2]. Problem You are not able to interact with the PSU instance using the Invoke-WebRequest PowerShell cmdlet even though logging in ...

    • KB0073 - Resetting PowerShell Universal configuration data

      Scope The scope of this document is applicable to all PowerShell Universal installations. Problem Incorrect configuration causes PowerShell Universal to behave in a manner that prevents the user from fixing the configuration. This can include ...