-
Bug
-
Resolution: Done
-
Critical
-
4.3.0.GA_CP06, EAP 5.0.0.BETA
-
None
When a SLSB annotated with @RunAs and @RunAsPrincipal invokes another SLSB, EJBContext.getCallerPrincipal invoked in the second SLSB returns the unauthenticatedIdentity and not the identity set with @RunAsPrincipal on the first SLSB as expected.
I will attach 2 example projects to demonstrate that.
- is blocked by
-
EJBTHREE-1892 @RunAsPrincipal not working as expected
- Closed
- is incorporated by
-
JBPAPP-2458 Upgrade EJB3 to 1.1.x
- Resolved
- is related to
-
JBPAPP-4503 ejb <run-as-principal> does not propagate beyond first call
- Closed
- relates to
-
JBPAPP-2500 @RunAsPrincipal not working as expected
- Closed
-
JBPAPP-1951 Caused by: java.lang.IllegalStateException: No valid security context for the caller identity when using @RunAsPrincipal
- Closed