[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2523) Identity component should be scoped to the WAR module

[Stuart Douglas (JIRA)]

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

Stuart Douglas updated JBSEAM-2523:
-----------------------------------

    Attachment: multiple-wars.diff


Patch that resolves the issue. The use of the static LifeCycle.application was causing the wrong identity component to be created in the IdentityFilter.

> Identity component should be scoped to the WAR module
> -----------------------------------------------------
>
>                 Key: JBSEAM-2523
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-2523
>             Project: Seam
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: 2.1.1.GA
>         Environment: JBoss 4.2.2.GA (also tested on 4.2.0.GA)
>            Reporter: Reind D
>            Assignee: Shane Bryzak
>         Attachments: multiple-wars.diff, seam2523.ear.tar.gz, seam2523.ear.tar.gz
>
>
> I have an EAR with two web modules. I have configured the 'Identity authenticateMethod' in components.xml to use a different a method for each WAR (authA.authenticate, authB.authenticate). When attempting to login to the 'b' webapp it invokes the authenticateMethod defined in a.war. Attempting to login to the 'a' webapp works as expected. It appears as though the Identity component is not scoped to the WAR. 
> The EAR is packaged as follows:
> my-application.ear/
>     a.war/
>         WEB-INF/
>             components.xml
>         ...
>     b.war/
>         WEB-INF/
>             components.xml
>         ...
>     web.jar
> Congure authentication as follows in both components.xml files:
> a.war/WEB-INF/components.xml
> <security:identity authenticate-method="#{authA.authenticate}" /> 
> b.war/WEB-INF/components.xml
> <security:identity authenticate-method="#{authB.authenticate}" /> 

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