[jboss-jira] [JBoss JIRA] Closed: (JBAS-6424) Stateless Session Bean getCallerPrincipal().getName() is cached between Remote Calls from Standalone Client with different User's

[Tom Iten (JIRA)]

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

Tom Iten closed JBAS-6424.
--------------------------

    Fix Version/s: JBossAS-5.0.1.GA
       Resolution: Done


With 5.0.1.GA it's working fine

> Stateless Session Bean getCallerPrincipal().getName() is cached between Remote Calls from Standalone Client with different User's
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-6424
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6424
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Security
>    Affects Versions: JBossAS-5.0.0.GA
>         Environment: Win XP, JBoss running on localhost
>            Reporter: Tom Iten
>            Assignee: Anil Saldhana
>             Fix For: JBossAS-5.0.1.GA
>
>
> Calling a Stateless Session Bean with different Users from a standalone Client delivers the same Principal Name.
> The roles of the different Users are correct. 
> Only the name of the Principal is always the name from the first invocation.
> The behaivor is testet with the simple Login Module and with JAAS Login. 
> For code snippets see also the jboss forum reference.

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