Blank App page with Window Authentication

Blank App page with Window Authentication

avatar
Product: PowerShell Universal
Version: 5.6.7


I am having a similar issue to these old threads

Infos: Universal v1.4.3 Dashboard v3.1.1 (Licensed) I’m using windows authentication, and roles have been defined by groupSid match against the claimsprincipal. All this is working fine… Issue: I’m thinking the -Role parameter in the New-UDPage function has an issue. When I use this, and the role matches, I get a page with no content. Proper theme, AppBar, and Title display fine… just no “page” content. If the role does not match the user I get the expected “? Page Not Found” error page …
Product: PowerShell Universal Version: 2.5.5 As outlined in a previous forum post new pages created with New-UDPage are not displaying when they are filtered to multiple security roles. I noticed this when upgrading from version 2.3 to 2.5.5. Not sure exactly when this bug was reintroduced. Is this a known issue? New-UDPage -Name "Working" -Url "/page/1" -Path "Page1.ps1" -Roles @("Role1") New-UDPage -Name "Not Working" -Url "/page/2" -Path "Page2.ps1" -Roles @("Role1", "Role2")
Product: PowerShell Universal Version: 2.0.3 When trying to set a new page with multiple roles for access, the page is displaying in the navigation menu when the user has the role to grant access. The page will display fine when there is one role been set however when more than one role has been set the page is in the navigation menu but the page is blank. Are multiple roles supported in pages? Example code below, logging in as a ServiceDeskAdmin all pages appear in the navigation menu but p…

Set up windows authentication, added the group claim to the admin role. I can see the claim passing correctly and I am getting the correct role when looking at My Identity



032cd79080da3618d6669672da3adda828692bbc
But when viewing an app that is set to only the admin role I get a completely blank page



697df7bb9f6b1ce680ac8bbbe2f522f1ff82a9ef
If I log in with the default local admin account the page loads fine.

697df7bb9f6b1ce680ac8bbbe2f522f1ff82a9ef.png

032cd79080da3618d6669672da3adda828692bbc.png

avatar
(anonymous user)

Recommended Answer

This was figured out on the Git issue. The problem is that my username was coming in as all uppercase, but was being saved as all lower case under identities. Manually modify the username to match uppercase and that fixed the issue.

All Comments (2)

avatar

github.com/ironmansoftware/powershell-universal
Looks like this popped up before here as well. I tried clearing the cached claims and restarting the service and I still get the same issue

avatar

This was figured out on the Git issue. The problem is that my username was coming in as all uppercase, but was being saved as all lower case under identities. Manually modify the username to match uppercase and that fixed the issue.