Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: 4.2.0.GA_CP09, 4.3.0.GA_CP08
Affects Version/s: 4.3.0.GA_CP06, EAP 5.0.0.BETA
Component/s: EJB, Security
Labels:
None

Affects:

Release Notes

When a SLSB annotated with @RunAs and @RunAsPrincipal invokes another SLSB, EJBContext.getCallerPrincipal invoked in the second SLSB returns the unauthenticatedIdentity and not the identity set with @RunAsPrincipal on the first SLSB as expected.
I will attach 2 example projects to demonstrate that.

is related to

JBPAPP-2473 @RunAsPrincipal not working as expected

Closed

JBPAPP-2786 REGRESSION -@RunAsPrincipal not working as expected

Closed

relates to

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

Closed

Assignee:: Carlo de Wolf

Reporter:: Marcus Moyses (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 2009/08/14 12:28 PM

Updated:: 2010/04/23 2:47 AM

Resolved:: 2010/02/23 3:48 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates