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

Not possible to create mechanism-provider-filtering-sasl-server-factory in Elytron configuration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.1.0.DR12
    • 7.1.0.DR9
    • Web Console
    • None
    • Hide
      1. start EAP with enabled Elytron subsystem
      2. using console navigate to Configuration: Subsystems > Subsystem: Security - Elytron > Settings: Factory
      3. create some SASL factory, e.g. Service Loader SASL Server 'test1'
      4. using New Mechanism Provider Filtering Sasl Server dialog try to create new factory with
      • Name: 'test2'
      • Sasl server factory: 'test1'
      Show
      start EAP with enabled Elytron subsystem using console navigate to Configuration: Subsystems > Subsystem: Security - Elytron > Settings: Factory create some SASL factory, e.g. Service Loader SASL Server 'test1' using New Mechanism Provider Filtering Sasl Server dialog try to create new factory with Name: 'test2' Sasl server factory: 'test1' 

      Last action resulted in an error

Unexpected HTTP response: 500

Request
{
    "name" => "test2",
    "sasl-server-factory" => "test1",
    "enabling" => false,
    "address" => [
        ("subsystem" => "elytron"),
        ("mechanism-provider-filtering-sasl-server-factory" => "test2")
    ],
    "operation" => "add"
}

Response

Internal Server Error
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException",
    "rolled-back" => true
}

      This is caused by missing required attribute filters. The dialog is missing any input fields for this list.

              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

                Created:
                Updated:
                Resolved: