Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-2523

Identity component should be scoped to the WAR module

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.1.1.GA
    • Fix Version/s: 2.2.0.CR1
    • Component/s: Security
    • Labels:
      None

      Description

      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}

      " />

        Gliffy Diagrams

          Attachments

          1. multiple-wars.diff
            2 kB
          2. seam2523.ear.tar.gz
            1.87 MB
          3. seam2523.ear.tar.gz
            1.85 MB

            Issue Links

              Activity

                People

                • Assignee:
                  shane.bryzak Shane Bryzak
                  Reporter:
                  reind Reind D
                • Votes:
                  7 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: