Uploaded image for project: 'Seam Security'
  1. Seam Security
  2. SEAMSECURITY-76

seam security external ScopeProducers don't work anywhere except AS6

        Details

        • Type: Bug
        • Status: Resolved (View Workflow)
        • Priority: Major
        • Resolution: Done
        • Affects Version/s: 3.0.0.Final
        • Fix Version/s: 3.1.0.Beta1
        • Labels:
          None

          Description

          The design of the Security External module depends on undefined behaviour of alternatives. It defines alternatives (*ApplicationScopeProducer and *VirtualApplicationScopeProducer) in the module and expects the application to set the alternatives in its beans.xml, which isn't supported by CDI spec (see CDI-18) and doesn't seem to work anywhere except JBoss AS 6.

          We should probably just remove the Producers and make the beans @ApplicationScoped directly. Users interested in changing the scope of those beans could still use Seam Config for that.

            Gliffy Diagrams

              Issue Links

              incorporates

              Bug - A problem which impairs or prevents the functions of the product. SEAMSECURITY-47 security-openid-rp - fails to deploy on GlassFish

              • Critical - An upcoming version that is affected by this issue cannot be released until it's addressed. A critical bug is one that crashes the application, causes loss of data or severe memory leak.
              • Resolved

                Activity

                Hide
                Permalink
                maschmid Marek Schmidt added a comment -

                fixed

                All the *ScopeProducers (such as OpenIdProviderInVirtualApplicationScopeProducer, OpenIdProviderInApplicationScopeProducer, ...) are @Vetoed, and to enable the specific producer, you now have to use, e.g.:

                <idp:SamlIdpInApplicationScopeProducer>
                <s:modifies/>
                </idp:SamlIdpInApplicationScopeProducer>

                in seam-beans.xml

                Show
                maschmid Marek Schmidt added a comment - fixed All the *ScopeProducers (such as OpenIdProviderInVirtualApplicationScopeProducer, OpenIdProviderInApplicationScopeProducer, ...) are @Vetoed, and to enable the specific producer, you now have to use, e.g.: <idp:SamlIdpInApplicationScopeProducer> <s:modifies/> </idp:SamlIdpInApplicationScopeProducer> in seam-beans.xml

                  People

                  • Assignee:
                    maschmid Marek Schmidt
                    Reporter:
                    maschmid Marek Schmidt
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved:

                      Development