Closed ccgthree closed 2 years ago
For anyone that runs into this issue, I found the solution. This particular error occurs when the scripts in c:\scripts\
(or wherever you've decided to maintain your scripts are still in a "blocked" state. To fix this issue, run the following command as an administrator:
Get-ChildItem -Path 'C:\scripts\' -Recurse | Unblock-File
If you've chosen to place your scripts in a different location, be sure to change that location in the Path parameter before running the command.
I'm seeing an "AuthorizationManager check failed." error upon successful login to a new instance of WebJEA and I'm unsure where to start when trying to pin down and fix the issue. This error may be related to issue number #22. However, that issue went stale and the user never reported back.
Any suggestions as to where I could/should start sniffing around to fix this issue?
Screenshot of Error
Log Contents for that Particular Session