PowerShell Universal - 5.0.5
PowerShell Universal - 5.0.5
Release Notes
APIs
- Fixed an issue where endpoint content wouldn’t be displayed in the admin console when using -Path
- Fixed an issue changing the path of endpoints (#3685)
Apps
- Fixed an issue where -DisableAutoStart had no affect (#3658)
- Fixed issue with -OnClick and -Theme on New-UDNivoChart (#3667)
- Added icon selector to page properties (#3678)
- Fixed an issue where a blank file and folder would be created if the app pointed to a path that didn’t exist (#3679)
- Fixed an issue where installing apps from the library wouldn’t show up (#3686)
Automation
- Added missing trigger schedule button
Platform
- Fixed an issue where the computer page would incorrectly show an error about the number of licensed computers.
- Fixed an issue where changing branding would duplicate lines in branding.ps1 (#3666)
- Fixed an issue with psudb.exe failing to convert jobs in certain configurations (#3670)
- Added permissive security model to cmdlets (#3676)
- Display number of selected changes in git commit (#3645)
- Fixed an issue where secret variable values would not be deleted from the database (#3654)
- Added missing clear cached claims button on the roles page.
- Fixed an issue running Connect-AzAccount
Downloads
Adam Driscoll
PowerShell Expert and Developer at Devolutions
All Comments (6)
Added permissive security model to cmdlets (#3676)
In light of this change, is it fair to assume that this is only temporary while you create a way for a token to be defined globally rather than needing each unauthenticated script or API to be modified in order to become authenticated prior to running its usual commands?
This effectively just reverts back to the v4 behavior. We are still deciding how to best handle it moving forward. I wouldn’t say this is temporary as this setting will remain but not clear on how else we will allow configuration of this.
We don’t really need a token because of how the internal auth works but we could have it so you could configure the default permissions granted to non-user-initiated scripts. We could also make it a bit more granular where you could specify it per environment or something. Probably a 5.1 thing.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
Thanks for the clarification and for making the transition from v4 to v5 easier.
How would I set this option?
Adam Driscoll
PowerShell Expert and Developer at Devolutions
I guess I need to improve my “search, find and don’t forget” skills…
Thank you.