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

[Frank Cornelis (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12462518#action_12462518 ] 

Frank Cornelis commented on JBSEAM-2523:
----------------------------------------

I'm experiencing the same issue. I've got a JBoss AS 5.0.1.GA where I've put all the 3th party JARs (including JBoss Seam 2.1.1.GA) under server/default/lib so my EARs are lightweight and build/deploy as fast as possible.

When I deploy only one EAR (JBoss Seam webapp with security:identity authenticate-method configured in components.xml) I can login as expected.

The second EAR (without security:identity authenticate-method configured in components.xml) makes the login of the first one to fail.

The error message I receive reads:
WARN  [IdentityManager] no identity store available - please configure an identityStore if identity management is required.
ERROR [SeamLoginModule] No authentication method defined - please define authenticate-method for <security:identity/> in components.xml

So it's pretty clear that JBoss Seam does not see the correct components.xml configuration file. Could someone correct this major scoping issue?

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