-
Feature Request
-
Resolution: Done
-
Blocker
-
None
-
None
Previously, with the Keycloak OIDC adapter, it was possible to propagate an identity from a WAR to an EJB when the WAR and EJB were packaged in an EAR. This was done by configuring Undertow and EJB to use the KeycloakDomain.
With the elytron-oidc-client subsystem, we now use a virtual security domain. With this approach, the identity can be successfully propagated from the web layer to the EJB layer when the EJB is contained in the same WAR. However, if the EJB is located outside the WAR and packaged in an EAR then the identity won't be propagated as described in this example.
More details can also be found in the comments in WFCORE-5178.
A related problem was also mention on the user forum about identity propagation across EARs.
- is cloned by
-
WFCORE-6190 Support for identity propagation from a WAR to an EJB in an EAR when using OIDC
- Closed
- is depended on by
-
WFLY-17312 Allow configuration of role claims for OpenID Connect
- Open
-
WFLY-17333 Allow Wildfly OIDC to be part of Elytron security domain / realms
- Open
- is related to
-
WFLY-17781 Ensure a virtual SecurityDomain is created if necessary when an EJB references a virtual security domain
- Closed
-
WFLY-17784 Add a test case that makes use of a virtual-security-domain with MP-JWT
- Closed
-
WFLY-17785 Fix intermittent failures in OidcIdentityPropagationTestCase
- Closed