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
But when viewing an app that is set to only the admin role I get a completely blank page
If I log in with the default local admin account the page loads fine.
opened 08:53PM - 28 Aug 24 UTC
closed 09:51PM - 02 Sep 24 UTC
bug
PowerShell Universal
requires triage
### Version
5.0.3
### Severity
Low
### Environment
msi
### Steps to Reprod… uce
Setup windows auth
Setup a role that maps a group SID to a role
Login with a user in that role
### Expected behavior
```console
Role is applied
```
### Actual behavior
```console
Role is not applied
```
### Additional Environment data
_No response_
### Screenshots/Animations
_No response_
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
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.
