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

[jbossseam-issues] [JBoss JIRA]...

Reind D (JIRA)

Tuesday, 22 January 2008 Tue, 22 Jan '08

9:05 p.m.

Identity component should be scoped to the WAR module ----------------------------------------------------- Key: JBSEAM-2523 URL: http://jira.jboss.com/jira/browse/JBSEAM-2523 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 2.0.1.CR1 Environment: JBoss 4.2.2.GA (also tested on 4.2.0.GA) Reporter: Reind D 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Reind D (JIRA)

Tuesday, 29 January Tue, 29 Jan

11:55 p.m.

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

[ http://jira.jboss.com/jira/browse/JBSEAM-2523?page=all ] Reind D closed JBSEAM-2523. --------------------------- Resolution: Rejected I was able to avoid this issue by removing the MyFacesExtensionsFilter: <filter> <filter-name>MyFacesExtensionsFilter</filter-name> <filter-class> org.apache.myfaces.webapp.filter.ExtensionsFilter </filter-class> <init-param> <description> Set the size limit for uploaded files. Format: 10 - 10 bytes 10k - 10 KB 10m - 10 MB 1g - 1 GB </description> <param-name>maxFileSize</param-name> <param-value>20m</param-value> </init-param> </filter> <filter-mapping> <filter-name>MyFacesExtensionsFilter</filter-name> <servlet-name>Faces Servlet</servlet-name> </filter-mapping> <filter-mapping> <filter-name>MyFacesExtensionsFilter</filter-name> <url-pattern>/faces/myFacesExtensionResource/*</url-pattern> </filter-mapping> Authentication works as expected after removing these lines from web.xml.

...

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Karl Traunmueller (JIRA)

Thursday, 4 December Thu, 4 Dec

4:37 p.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Karl Traunmueller commented on JBSEAM-2523: ------------------------------------------- I have the exact same problem as explained in the description, Seam 2.1.0.SP1 on JBoss EAP 4.3.0.GA_CP01 Why has this issue been rejected? I'm sure it's a reproducible bug. And I don't think it has anything to do with MyFaces, since we're not using any MyFaces stuff in our project... Could you please reopen and fix this isse? regards, Karl

...

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.0.1.CR1 Environment: JBoss 4.2.2.GA (also tested on 4.2.0.GA) Reporter: Reind D 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

Reind D (JIRA)

Thursday, 25 December Thu, 25 Dec

12:14 a.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Reind D reopened JBSEAM-2523: ----------------------------- After upgrading to Seam 2.1.1.GA, I'm experiencing this issue again. I suspect that the earlier resolution was a coincidence as the above poster suggests. I'll create an example EAR that demonstrates this bug.

...

Reind D (JIRA)

Wednesday, 31 December Wed, 31 Dec

5:35 p.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Reind D updated JBSEAM-2523: ---------------------------- Affects Version/s: 2.1.1.GA (was: 2.0.1.CR1)

...

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 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}" />

Reind D (JIRA)

Friday, 2 January Fri, 2 Jan

10:55 p.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Reind D updated JBSEAM-2523: ---------------------------- Attachment: seam2523.ear.tar.gz 1. Deploy the ear. 2. Go to http://localhost:8080/a/ 3. Enter any user & pass, and hit the login button. Note that the text "**** in B.login() ****" is output to the server log. Instead, this should say "in A.login()". It's calling B.login() instead of A.login() as configured in a.war/WEB-INF/components.xml 4. Repeat steps 2-3 on http://localhost:8080/b/ and note that the message indicates that B.login() is invoked (as expected, this time). This example is intended to be deployed to JBoss 5.0.0.GA Note: It's included here as a tar.gz file b/c jboss5 has issues deploying it as a zipped ear. Please unzip and deploy the exploded ear.

...

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 Attachments: 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}" />

Reind D (JIRA)

11 p.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Reind D commented on JBSEAM-2523: --------------------------------- I noticed that this issues does not occur if I comment out the "Seam Filter" from both WARs. This can be reproduced in the attached project.

...

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 Attachments: 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}" />

Reind D (JIRA)

Saturday, 3 January Sat, 3 Jan

12:09 a.m.

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

...

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 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}" />

Shane Bryzak (JIRA)

Thursday, 16 April Thu, 16 Apr

12:29 a.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Shane Bryzak reassigned JBSEAM-2523: ------------------------------------ Assignee: Shane Bryzak

...

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}" />

Frank Cornelis (JIRA)

11:29 a.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] 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}" />

Stuart Douglas (JIRA)

Wednesday, 22 April Wed, 22 Apr

7:51 a.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] 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}" />

Shane Bryzak (JIRA)

8:25 a.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Shane Bryzak closed JBSEAM-2523. -------------------------------- Fix Version/s: 2.1.2.CR2 Resolution: Done Thanks Stuart, I've applied your patch to the Seam_2_1 branch.

...

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 Fix For: 2.1.2.CR2 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}" />

Stuart Douglas (JIRA)

Monday, 4 May Mon, 4 May

12:33 a.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Stuart Douglas commented on JBSEAM-2523: ---------------------------------------- This should probably be re-opened, as the patch was reverted.

...

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 Fix For: 2.1.2.CR2 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}" />

Frank Cornelis (JIRA)

Friday, 12 June Fri, 12 Jun

6:41 a.m.

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

...

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 Fix For: 2.1.2.CR2 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}" />

Pete Muir (JIRA)

11:56 a.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Pete Muir reopened JBSEAM-2523: ------------------------------- Reopen for reverted patch.

...

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 Fix For: 2.1.2.CR2 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}" />

Pete Muir (JIRA)

Tuesday, 16 June Tue, 16 Jun

4:34 p.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Pete Muir updated JBSEAM-2523: ------------------------------ Fix Version/s: 2.2.0.CR1 (was: 2.1.2.CR2)

...

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 Fix For: 2.2.0.CR1 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}" />

Pete Muir (JIRA)

4:34 p.m.

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

[ https://jira.jboss.org/jira/browse/JBSEAM-2523?page=com.atlassian.jira.pl... ] Pete Muir closed JBSEAM-2523. ----------------------------- Resolution: Done Reind reports fixed

...

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 Fix For: 2.2.0.CR1 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}" />

5494

days inactive

6005

days old

seam-issues@lists.jboss.org

Manage subscription

16 comments

6 participants

tags (0)

participants (6)

Frank Cornelis (JIRA)
Karl Traunmueller (JIRA)
Pete Muir (JIRA)
Reind D (JIRA)
Shane Bryzak (JIRA)
Stuart Douglas (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

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