[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1945) RunAsIdentity is not propagated correctly
[
https://jira.jboss.org/browse/EJBTHREE-1945?page=com.atlassian.jira.plugi...
]
Pappy STANESCU updated EJBTHREE-1945:
-------------------------------------
Attachment: EJBTHREE-1945.zip
Hi
Here is a small application covering three cases
- invocation from a MDB annotated with @RunAs
- invocation from a Servlet annotated with @RunAs
- invocation from a servlet with authentication
Only the third works, the first two fail with "Caller Unauthorized".
The deployable artefacts are in the deploy/ directory of the archive
RunAsIdentity is not propagated correctly
-----------------------------------------
Key: EJBTHREE-1945
URL: https://jira.jboss.org/browse/EJBTHREE-1945
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: Plugin 1.0.17
Reporter: Anton Kolmakov
Assignee: Carlo de Wolf
Fix For: depchain-1.0.0-alpha-2
Attachments: EJBTHREE-1945.zip
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira