Script Execution from Dashboard
Product: PowerShell Universal Version: 4.5.5
I'm having an issue with a standard user execution a script from a Dashboard. I have 2 environments currently, both running 4.5.5 (yeah, I know it's older, looking to rebuild our 'prod' environment with 2026 but i need to have a 'dev' version for users to use while I rebuild it), but users are not able to run scripts from a dashboard. The error that I get in the admin portal is
Error executing job: The credential '************' can not be used for the roles '****,****'.
Our old environment, which has been upgraded several times and was created using PUD version 2.X, is working perfectly fine. I've checked all the settings in the admin portal and everything looks mirrored. Has anyone encountered this issue or can direct me to look in some place? Thanks in advance!
Recommended Answer
@btull I believe that's the case in v4. You might be able to edit the variables.ps1 file and reload the configuration for it but it might be easier to just delete and re-add the secret. In 2026 you can edit the properties and value of secrets in the console.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
All Comments (6)
@btull I would double check how the secret variable for the credential running the script is defined. If it has roles associated with it, and the user using the dashboard does not have that role, then they would see this error. You can either remove the roles from the variable or add one of the user's roles to that variable.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
@btull I would double check how the secret variable for the credential running the script is defined. If it has roles associated with it, and the user using the dashboard does not have that role, then they would see this error. You can either remove the roles from the variable or add one of the user's roles to that variable.
Thanks @Adam Driscoll . That looks spot on, based on the included photo! Even though the account running PU is set as an 'Administrator', does that not cover all roles? Secondly, since it's a secret, it looks like I can't edit it. So, I would need to remove it and re-add it using the correct role(s), or no roles at all?
72c965bd-5d88-48e4-9868-3ff4b93b7f84.png
@btull I believe that's the case in v4. You might be able to edit the variables.ps1 file and reload the configuration for it but it might be easier to just delete and re-add the secret. In 2026 you can edit the properties and value of secrets in the console.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
@btull I believe that's the case in v4. You might be able to edit the variables.ps1 file and reload the configuration for it but it might be easier to just delete and re-add the secret. In 2026 you can edit the properties and value of secrets in the console.
@Adam Driscoll
Thanks! Checking that now, I'll update the ticket depending on the outcome.
@Adam Driscoll Looks like that was the fix! I didn't even think to look there. Thanks a bunch!
@btull Great! Glad that got it working for you!
Adam Driscoll
PowerShell Expert and Developer at Devolutions