Hi Srinivas, for TomEE 1.7 not sure what to say, we can only propagate the security context in the environment we know. ee-concurrency utilities is like any custom executor service for JavaEE 6 (= not known).
for TomEE 7 it will get fixed for next release ( https://issues.apache.org/jira/browse/TOMEE-1695). Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2016-01-20 9:48 GMT+01:00 seenu.atluri <[email protected]>: > Hi Romain, > > I created a sample app on top of tomee example "rest-jaas". It is > exhibiting > the same behavior. Security context is not being propagated when request is > processed asynchronously. Otherwise, it is working fine. > > Here is the sample I created. > > https://github.com/atluri64/tomee-jaas > > Try accessing the URL "http://localhost:8080/rest-jaas/async"; to test it. > > Thanks & Regards, > Srinivas Atluri. > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/TomEE-security-context-is-not-getting-propagated-with-WorkManagers-tp4677483p4677502.html > Sent from the TomEE Dev mailing list archive at Nabble.com. >
