My 3.9.17 instance is prompting me about an available update to 4.1.0 - but I don’t think it would be a wise move to simply update from v3 to v4 just like any other update?
Agreed, this is in my laptop development environment where I construct my code prior to going to Dev, Test, and Prod.
This release has some new functionality in I have been waiting for to implement.
In the meantime, I have spun up a separate container for testing, but at some point i will need to upgrade my current laptop docker environment.
4.0.12 works fine for me… The only problems i had was with new-udhelmet being in the modules’ folder which is now packaged in the product, so once that was removed it all worked.
after updating to 4.1.0 i’m getting forwarded to ‘/service-catalog’ after logging in, without receiving any kind of html. When trying to access ‘/admin’ manually, i’m getting unautharized access returned.
I can see how this would happen but it would have to have the following conditions:
No dashboard or page set to the baseURL of /
User that is logging in is not in a built in role (Admin, operator, executor, reader)
My hunch is that you were caught by the change where the admin role is not being applied by default and you may need to adjust the roles.ps1 script to grant that role.
Thanks for your quick response!
That could very well be the case, as far as i understand the docs the roles.ps1 script should be under ‘Repository.universal’ however, that doesn’t seem to be the case for me. In case i have to create and alter it myself, can you give me a pointer how to manually add the Admin role to my account?
Thanks a lot.
Edit: @Matt.Harris We are on WinServer 2019, using default deployment as a windows service.
I just tried to permit the login by altering the auth.ps1 script, however that didn’t lead to success.
One more thing: Directly accessing Apps by their URL still works, so i guess you were right @adam
So i need to set the role and also set the baseURL of /?
Can i access some kind of shell of PSU running in a service? Sorry if i am missing something obvious, we are still in the early stages of deployment so it’s my first time troubleshooting something PSU related.
Thanks!
New-PSURole -Name "Administrator" -Description "Administrators can manage settings of PSU, create and edit any entity within PSU and view all the entities within PSU." -Policy {
param(
$User
)
$true
}
The other roles were disabled by default.
New-PSURole -Name "Operator" -Description "Operators have access to manage and execute scripts, create other entities within PowerShell Universal but cannot manage PowerShell Universal itself." -Policy {
param(
$User
)
$false
}
