-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
7.4.7.GA, 8.0.0.Beta
-
False
-
None
-
False
-
-
-
-
-
-
-
The JSR 345: Enterprise JavaBeans 3.2 specification defines that propagation must behave exactly the same behavior between sync and async. When using the SecurityContext.getCallerPrincipal, the used Eclipse Soteria implementation of the Java EE Security API Specification is delegating to EJBContext.getCallerPrincipal which obtains the custom principal correctly. This principal is returned only if it is of CallerPrincipal type. This fix is to return the principal from EJBContext whether it is of type CallerPrincipal or not.
- clones
-
JBEAP-24199 [GSS](7.4.z) WFLY-17316 - SecurityContext callerPrincipal not set with Asynchronous tagged EJB
- Closed
- is cloned by
-
WFLY-17316 SecurityContext callerPrincipal not set with Asynchronous tagged EJB
- Closed
- is incorporated by
-
JBEAP-24210 (8.0.z) Upgrade Soteria from 3.0.0 to ...
- Closed