WildFly Elytron: OIDC app attempting to access the second tenant, the user should be prompted to log
High severity
GitHub Reviewed
Published
Apr 10, 2024
to the GitHub Advisory Database
•
Updated Jun 18, 2024
Package
Affected versions
< 2.2.5.Final
Patched versions
2.2.5.Final
Description
Published by the National Vulnerability Database
Apr 10, 2024
Published to the GitHub Advisory Database
Apr 10, 2024
Reviewed
Apr 10, 2024
Last updated
Jun 18, 2024
A flaw was found in JBoss EAP. When an OIDC app that serves multiple tenants attempts to access the second tenant, it should prompt the user to log in again since the second tenant is secured with a different OIDC configuration. The underlying issue is in OidcSessionTokenStore when determining if a cached token should be used or not. This logic needs to be updated to take into account the new "provider-url" option in addition to the "realm" option.
References