[jboss-jira] [JBoss JIRA] Updated: (SECURITY-237) Create different implementation of JaasSecurityManager

[Anil Saldhana (JIRA)]

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

Anil Saldhana updated SECURITY-237:
-----------------------------------

        Fix Version/s: 2.0.2.CR4
                           (was: 2.0.2.GA)
    Affects Version/s: 2.0.2.CR3
                           (was: 2.0.2.CR7)


> Create different implementation of JaasSecurityManager
> ------------------------------------------------------
>
>                 Key: SECURITY-237
>                 URL: https://jira.jboss.org/jira/browse/SECURITY-237
>             Project: JBoss Security and Identity Management
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: JBossSX
>    Affects Versions: 2.0.2.CR3
>            Reporter: Marcus Moyses
>            Assignee: Marcus Moyses
>             Fix For: 2.0.2.CR4
>
>
> The current implementation of the JaasSecurityManager could lead to a problem where multiple threads try to authenticate concurrently.
> Both threads would try to validate the principal in the cache and fail (as the principal has not logged in yet) and proceed to authentication. The first threads authenticates the principal, but the second one removes that entry from the cache (causing a logout) and authenticates the principal again.
> One solution is to make cache validation and authentication an atomic operation, synchronized on the principal's name.

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