[jboss-jira] [JBoss JIRA] Updated: (JBAS-5600) Security Context is remote if it comes as part of invocation

[Jason T. Greene (JIRA)]

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

Jason T. Greene updated JBAS-5600:
----------------------------------

    Fix Version/s: Unscheduled
                       (was: 6.0.0.M3)


Unscheduling due to inactivity. Reassign to a release that you feel comfortable resolving this issue in, or leave as is.

> Security Context is remote if it comes as part of invocation
> ------------------------------------------------------------
>
>                 Key: JBAS-5600
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5600
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: EJB2, Security
>    Affects Versions: JBossAS-5.0.0.Beta4
>            Reporter: Anil Saldhana
>            Assignee: Anil Saldhana
>             Fix For: Unscheduled
>
>
> I need to look further into the logic used in PreSecurityInterceptor. I may be doing way too much to derive whether the call was remote or local and accordingly set the security context on the association. The simplest may be to just assume that if there is a security context in the invocation, then it can be inter-vm.
> Both PresecurityInterceptor and SecurityInterceptor are affected by this change.

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