[2026.3.0] /hangfire access denied

Hello @Matthew Morrow

Thank you again for your continued collaboration and for taking the time to test PowerShell Universal 2026.3.0 so thoroughly.

We appreciate the multiple reports you have shared while working with this new release. Feedback like this is especially helpful as we review behavior introduced or observed in the latest version.

For this specific report, we will review the HTTP 403 response when accessing /hangfire and attempt to reproduce the behavior internally under comparable conditions. We will update the thread once we have additional findings or need specific environment details from you.

Thank you again for documenting these issues and helping us investigate them.

Best regards,
Ruben Tapia

Hi @Matthew Morrow
We have made progress reviewing the HTTP 403 behavior when accessing /hangfire.

Our current analysis shows that access to the Hangfire dashboard includes a specific Administrator role authorization check. However, before reaching a final conclusion, we still need to complete additional runtime testing under comparable authentication conditions to determine why the authorized browser session is receiving the 403 response.

We will continue the validation and update this thread once those tests are complete.

Best regards,
Ruben Tapia

Hello @Matthew Morrow

Thank you again for your continued collaboration while we review these reports in PowerShell Universal 2026.3.0.

We completed the targeted validation for this case. In our controlled test, /hangfire behaved as follows:

• Administrator role: HTTP 200 and the Hangfire dashboard loaded successfully.
• Non-Administrator role: HTTP 403.
• Unauthenticated session: redirected to the login page.

We also confirmed that access to /hangfire is evaluated against the PowerShell Universal Administrator role.

Before we can move this case forward for internal escalation like the other reports, we need to validate one remaining point in your environment:

Can you confirm whether the account receiving the HTTP 403 is assigned the Administrator role in PowerShell Universal?

If it is, please also sign out completely, start a fresh session, sign back in with that Administrator account, and confirm whether /hangfire still returns HTTP 403.

If a confirmed Administrator session continues to receive HTTP 403, that would give us the additional runtime evidence needed to evaluate this case for escalation.

Best regards,
Ruben Tapia

its working now for me in 26.3.1.0