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

Filters table of Mechanism Provider Filtering Sasl Server factory doesn't show default version comparison

    XMLWordPrintable

Details

    • Hide
      1. start EAP with enabled Elytron subsystem
      2. create factory:
        1. /subsystem=elytron/provider-loader=test-provider-loader:add
        2. /subsystem=elytron/provider-sasl-server-factory=test-sasl-factory:add(provider-loader=test-provider-loader)
        3. /subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=test-filtering-sasl-factory:add(sasl-server-factory=test-sasl-factory,filters=[ {provider-name=test-provider-name,provider-version=123}

          ])

      3. using web console navigate to Configuration: Subsystems > Subsystem: Security - Elytron > Settings: Factory
      Show
      start EAP with enabled Elytron subsystem create factory: /subsystem=elytron/provider-loader=test-provider-loader:add /subsystem=elytron/provider-sasl-server-factory=test-sasl-factory:add(provider-loader=test-provider-loader) /subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=test-filtering-sasl-factory:add(sasl-server-factory=test-sasl-factory,filters=[ {provider-name=test-provider-name,provider-version=123} ]) using web console navigate to Configuration: Subsystems > Subsystem: Security - Elytron > Settings: Factory

    Description

      version-comparison shouldn't be empty, at least when provider-version is not empty.
      Please show default value if not explicitly set.
      I don't want to force user remember if default version-comparison is less-than or greater-than.

      Attachments

        Issue Links

          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) HAL-1264 Show defaul value for version-comparison attribute in mechanism-provider-filtering-sasl-server-factory view

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-8408 (7.1.0) Upgrade HAL to 2.9.1.Final

          • 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

              cmiranda@redhat.com Claudio Miranda
              pjelinek@redhat.com Pavel Jelinek
              Pavel Jelinek Pavel Jelinek
              Pavel Jelinek Pavel Jelinek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: