Closed adamdriscoll closed 2 months ago
I have been able to reproduce the child script not accessing secret variables with roles. What I found was that this would only happen sometimes. We had a check for $null in the code base that should have been checking for an empty string as well. If it was an empty string, then the check would fail and we wouldn't properly communicate the user's roles down the child script and thus the secrets wouldn't work. This will be fixed in 4.3.4.
I'm running a nightly build if anyone wants to test that.
As for the NotAuthorized issue, it looks like that is coming of our access control service but I can't get it to trigger in my environment.
Version
4.3.2
Severity
High
Environment
msi
Steps to Reproduce
https://forums.ironmansoftware.com/t/invoke-psuscript-in-4-3-3-gets-not-authorized-worked-in-4-3-2/11010/15 https://forums.ironmansoftware.com/t/secrets-are-not-available-in-sub-script-how-to-fix/10953/19
Some example configurations that may cause this:
Access controls on a custom role that allow access to scripts.
I cannot reproduce this. Current configuration:
Access Controls
Roles
Expected behavior
Users
User's view of the admin console
User Running a Script
Parent Script
Child Script
Variables
Actual behavior
Additional Environment data
No response
Screenshots/Animations
No response