[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1945) RunAsIdentity is not propagated correctly

Sat Oct 31 03:26:05 EDT 2009

     [ https://jira.jboss.org/jira/browse/EJBTHREE-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anton Kolmakov updated EJBTHREE-1945:
-------------------------------------

    Description: 
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 @RunAsPrincipal annotation.

  was:
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.
RunAsPrincipal is propagated to B only but not to C. 

Why? Is it expected behavior? 
I expect propagation of RunAsPrinciapl to all beans in execution chain after bean with @RunAsPrincipal annotation.

> 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
>
> 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 @RunAsPrincipal annotation.

-- 
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