Red Hat Bugzilla – Bug 1005093
Security context associated with EJB asynchronous invocations can potentially be corrupted over time by the caller thread
Last modified: 2014-05-26 21:28:03 EDT
Consider a servlet "S" which invokes on a asynchronous EJB "A". Let's assume "S" runs with a "foo" run-as role. Now when S invokes on "A", the run-as "foo" role is correctly propagated to the asynchronous EJB invocation. However, when the "S" invocation completes and potentially clears the security context (of any run-as role), the invocation(s) within the asynchronous EJB "A" too lose the corresponding security context role association. This is because the 2 threads (the servlet invocation one and the async EJB invocation one) literally share the same object instance of the SecurityContext.
The expected behaviour is that the original security context (attributes) are copied over to the async invocation and updates to that security context later on in a separate thread shouldn't affect the ongoing async EJB invocation.
Verified in EAP 6.2.0.ER1.
Assigning firstname.lastname@example.org EJB issues to email@example.com. Please re-assign to Cheng or others as needed.
*** Bug 1032188 has been marked as a duplicate of this bug. ***