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

    • 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

      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.

        1. factory-filters.png
          factory-filters.png
          105 kB

              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:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: