Loading...

XML

Word

Printable

Type: Bug
Resolution: Cannot Reproduce
Priority: Major
Fix Version/s: TBD EAP 5
Affects Version/s: EAP 5.0.1
Component/s: None
Labels:
None

Release Note Status:
Not Required

If you have SessionBeanA calling a method in SessionBeanB which calls a method in SessionBeanC

When using the <run-as-principal> in SessionBeanA the principal set by <run-as-principal> correctly propagates to SessionBeanB but not to SessionBeanC.

It should propagate through the call stack.

is related to

EJBTHREE-1945 RunAsIdentity is not propagated correctly

Closed

JBAS-1389 run-as-principal only propogates one level

Closed

relates to

JBPAPP-2786 REGRESSION -@RunAsPrincipal not working as expected

Closed

JBPAPP-1951 Caused by: java.lang.IllegalStateException: No valid security context for the caller identity when using @RunAsPrincipal

Closed

Assignee:: Carlo de Wolf

Reporter:: Shaun Appleton

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2010/06/18 11:36 AM

Updated:: 2011/02/08 5:50 PM

Resolved:: 2011/02/08 5:50 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates