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

The server boot failure after unsetting the filter attribute in mechanism-provider-filtering-sasl-server-factory (Elytron)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.DR11
    • 7.1.0.DR9
    • Management, Security
    • None
    • Hide 
      jboss-eap-7.1/bin/standalone.sh -c standalone-elytron.xml
jboss-eap-7.1/bin/jboss-cli.sh -c << EOT
/subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=elytron:add
/subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=elytron:undefine-attribute(name=filters)
reload
EOT
      Show
      jboss-eap-7.1/bin/standalone.sh -c standalone-elytron.xml jboss-eap-7.1/bin/jboss-cli.sh -c << EOT /subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=elytron:add /subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=elytron:undefine-attribute(name=filters) reload EOT

    Description

      A duplicate resource failure followed by removing filters attribute in /subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=elytron and reload results in server boot failure.

      15:50:29,961 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
15:50:29,974 INFO  [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Alpha13-redhat-1) stopped in 7ms

      Why it's a blocker?

      • because the unsetting of the required attribute is allowed, customers can simply end up with dead EAP (by common sense they could expect that removing all filters mean allowing all SASL factories)
      • it seems the first (failed) command doesn't do a correct clean up and it results in problems during subsequent CLI operations

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7981 The server boot failure after unsetting the filter attribute in mechanism-provider-filtering-sasl-server-factory (Elytron)

          • 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.
          • Closed
          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-7248 Elytron mechanism-provider-filtering-sasl-server-factory cannot be added without filters attribute in CLI

          • 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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-8449 Upgrade to Elytron Subsystem 1.0.0.Beta2

          • 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
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: