[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1945) RunAsIdentity is not propagated correctly
[
https://jira.jboss.org/jira/browse/EJBTHREE-1945?page=com.atlassian.jira....
]
Radovan Bauer commented on EJBTHREE-1945:
-----------------------------------------
I can confirm this behavior also for ordinary Stateless beans.
The RunAsIdentity is used only for the first-level calls.
This renders @RunAs quite useless, because I cannot make calls to secured services
from other beans when using RunAsIdentity.
RunAsIdentity is not propagated correctly
-----------------------------------------
Key: EJBTHREE-1945
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1945
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: Plugin 1.0.17
Reporter: Anton Kolmakov
Assignee: jaikiran pai
I have one message driven bean A and two stateless beans B and C.
A annotated with @RunAs, @RunAsPrincipal and @SecurityDomain.
B and C annotated with @SecurityDomain.
A receives message and calls B which calls C.
RunAsIdentity is propagated to B only but not to C.
Why? Is it expected behavior?
I expect propagation of RunAsIdentity to all beans in execution chain after bean with
@RunAs* annotations.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira