AuthorizationManager check failed - Existing Dashboards on new server running 2.11.0

Product: PowerShell Universal
Version: 2.11.0

I setup a new server to test 2.11.0. Most of my dashboards have pages with -Role defined on them. I am getting this error message on my dashboards:
image

I’m not finding this error message in my logs, and haven’t made any changes to how my roles work in 2.9.3. Any ideas on where to look for more info on this error?

I am using Azure AD for authentication and the one dashboard that is working does show the claims coming across properly.

I just found out that this is an issue with dashboards running in the integrated environment. If I move them to a custom environment or default, it seems to work.

Is there a change in the integrated environment around authorization?

The AuthorizationManager check actually doesn’t have to do with PSU authorization but rather a component of PowerShell.

It could be that something isn’t signed correctly on our end (like the PSM1 file for the dashboard) or that the files are not unblocked (Unblock-File)

Is there a way to see what module/cmdlet/file may be causing this?

You should be able to check in the dashboard log.

I have the same issue after a big jump upgrade from 1.5.16 to 3.6.5.

All dashboard buttons result in AuthorizationManager errors. I see nothing in my dashboard log except its startup results, which are clean. Certainly no time-based logging such as that shown in adam’s screenshot.

I have unblocked the world. So that’s not the issue.
image

I suppose I should add that I don’t even know what to look at to troubleshoot. What are the options? Don’t know why I don’t have logging information.

I’ve tested a fresh, blank dashboard with default settings and it shows me the same error on its Home page.

Can you verify that when you ran Unblock-File you had elevated your command prompt as administrator? Unblock-File won’t throw any errors if it can’t access the file and they are actually still blocked.

I did not know that. Thanks for pointing that out. I wish it was the case I wasn’t an admin, but I’ve confirmed (still had the shell open) that I was. I ran the command on both the unzipped web/application folder and the UniversalAutomation folder under ProgramData.

Discovered my own error. I neglected to recurse when unblocking files within the unzipped site/application directory. Thanks for your help, Adam.

1 Like