An issue exists where a request's authorization scope could persist into subsequent requests on the same route when using a supported authz-keycloak configuration. This leads to unintended authorization expansion and inconsistent access-control decisions, potentially exposing data elements to the wrong session.