[jboss-jira] [JBoss JIRA] (AS7-4689) SimpleSecurityManager and JBossCachedAuthenticationManager do not work together correctly when calling remote ejb

[jaikiran pai (JIRA)]

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

jaikiran pai updated AS7-4689:
------------------------------

    Affects Version/s: 7.1.1.Final
                           (was: 7.1.2.Final (EAP))
      Forum Reference: https://community.jboss.org/message/732713#732713, https://community.jboss.org/message/732715  (was: https://community.jboss.org/message/732713#732713, https://community.jboss.org/message/732715)

    
> SimpleSecurityManager and JBossCachedAuthenticationManager do not work together correctly when calling remote ejb
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-4689
>                 URL: https://issues.jboss.org/browse/AS7-4689
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 7.1.1.Final
>            Reporter: Michael Gronau
>            Assignee: jaikiran pai
>              Labels: authentication, ejb, jaas
>
> the method SimpleSecurityManager.push(...) is called for every ejb call and here for every call a new instance of SimplePrincipal is created for the SubjectInfo. Then the method authenticate() is called. Here it delegates to the JBossCachedAuthenticationManager which tries to find an already cached principal, but this cannot work, because the get() function of the cache returns null. It returns null, because of the newly created SimplePrincipal for the current invocation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira