Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-17020

(7.2.z) ELY-1810 - (Intermittent) stuck start with secmgr after enabling Elytron JACC for undertow/application-security-domain

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.2.3.CR1, 7.2.3.GA
    • None
    • Security
    • None
    • Hide

      Switch to Elytron and run

      • ./bin/jboss-cli.sh --file=docs/examples/enable-elytron.cli
      • ./bin/standalone.sh -secmgr

      Configure and reload

      • /subsystem=security:write-attribute(name=initialize-jacc,value=false)
      • /subsystem=elytron/policy=jacc:add(jacc-policy={})
      • reload
      • /subsystem=undertow/application-security-domain=other:write-attribute(name=enable-jacc,value=true)
      • reload

      Stop and start several times

      • Ctrl-C
      • ./bin/standalone.sh -secmgr
      Show
      Switch to Elytron and run ./bin/jboss-cli.sh --file=docs/examples/enable-elytron.cli ./bin/standalone.sh -secmgr Configure and reload /subsystem=security:write-attribute(name=initialize-jacc,value=false) /subsystem=elytron/policy=jacc:add(jacc-policy={}) reload /subsystem=undertow/application-security-domain=other:write-attribute(name=enable-jacc,value=true) reload Stop and start several times Ctrl-C ./bin/standalone.sh -secmgr

    Description

      After enabling JACC on undertow/application-security-domain=other, the server can get stuck when starting with Security Manager turned on. It stops responding and cannot be terminated by Ctrl-C.

      After disabling JACC, or when starting without Security Manager, the server starts as expected.

      This behaviour blocks customers that uses JACC with Security Manager.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. ELY-1810 (Intermittent) stuck start with secmgr after enabling Elytron JACC for undertow/application-security-domain

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-16838 [GSS](7.2.z) Upgrade Wildfly Elytron from 1.6.2 to 1.6.3

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              rhn-support-ivassile Ilia Vassilev
              okotek@redhat.com Ondrej Kotek
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: