[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-741) Aspects RunAsSecurityInterceptors should push the current RunAsIdentity onto the stack
[ http://jira.jboss.com/jira/browse/EJBTHREE-741?page=comments#action_12345188 ]
Anil Saldhana commented on EJBTHREE-741:
----------------------------------------
Anil: - Even if the current RunAsIdentity for the component in question is null, we push
it such that a peek at the Run As stack at a depth of 1 always returns the caller's
RAI.
Scott::- Yes, that way its always push going in, pop going out as opposed to trying to
keep track of the whether or not something was pushed.
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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira