]
Anil Saldhana closed EJBTHREE-741.
----------------------------------
Resolution: Done
Aspects RunAsSecurityInterceptors should push the current
RunAsIdentity onto the stack
--------------------------------------------------------------------------------------
Key: EJBTHREE-741
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-741
Project: EJB 3.0
Issue Type: Bug
Components: Security
Affects Versions: EJB 3.0 RC9 - FD
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: EJB 3.0 RC10 - FD
Irrespective of whether the current ejb defines a RunAs annotation or not, there is a
need to push the current RunAsIdentity (can be null) on the RunAs stack in the
SecurityAssociation RunAs stack such that a peek into the stack at a depth of 1, always
returns the correct RunAsIdentity of the caller. Note that depth 0, would be the current
RunAsIdentity of the bean/component in consideration.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: