-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
1.3.0
-
False
-
-
False
-
-
-
Moderate
Description of the problem:
Given an RHDH + Orchestrator instance with RBAC enabled, it takes 30 seconds to show a user that is denied via RBAC that they are unable to access the Orchestrator section. This occurs for an implicitly denied user (no role assigned via rbac) and an explicitly denied user (RBAC role denying access). User is eventually denied as expected.
Users with access can get in right away.
How reproducible:
100% so far
Steps to reproduce:
1. Deployed RHDH + Orchestrator 1.3
2. Enable RBAC
3. RH SSO Keycloak (local instance) is the idp for this case
4. Create an RBAC policy that denies access to Orchestrator
5. Try to access with user associated with deny RBAC or user with no RBAC roles assigned
Actual results:
Page will appear to load for 30 seconds then show the expected error (504 currently)
Expected results:
User is denied close to immediately