-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
---
-
---
Currently, attempting to propagate an identity from a servlet within one deployment to an EJB within another deployment associated with a different security domain fails even when outflow-security-domains and trusted-security-domains are configured. The underlying problem is that outflow is not actually triggered in this case. To activate any outflow identities automatically, one option is to add a global EJB client interceptor that would ensure that we always runAs the current security identity.
- depends on
-
-
- Closed
-
- is blocked by
-
WFLY-9976 EJB Client Interceptor not invoked for Local Interface
-
- Coding In Progress
-
- is incorporated by
-
JBEAP-24228 [GSS](7.4.z) Add a global EJB client interceptor for EJB deployments that will runAs the current security identity to activate any outflow identities
-
- Verified
-
