Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-7575

Elytron mechanism-provider-filtering-sasl-server-factory cannot be added without filters attribute in CLI

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 11.0.0.Alpha1
    • None
    • Security
    • None
    • Hide

      1) Start server with standalone-elytron.xml
      2) Run CLI command

      /subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=factory:add(sasl-server-factory=global)
{
    "outcome" => "failed",
    "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException",
    "rolled-back" => true
}

      You will see exception in server log.
      3) Following CLI add mechanism-provider-filtering-sasl-server-factory

      /subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=factory:add(sasl-server-factory=global,filters=[{provider-name=someProvider}])
      Show
      1) Start server with standalone-elytron.xml 2) Run CLI command /subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=factory:add(sasl-server-factory=global) { "outcome" => "failed" , "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException" , "rolled-back" => true } You will see exception in server log. 3) Following CLI add mechanism-provider-filtering-sasl-server-factory /subsystem=elytron/mechanism-provider-filtering-sasl-server-factory=factory:add(sasl-server-factory=global,filters=[{provider-name=someProvider}])

      Adding mechanism-provider-filtering-sasl-server-factory without filters attribute through CLI causes IllegalArgumentException. Exception is not thrown when filters attribute is used.

      It has to be decided whether:

      • filters should be required, then its nillable should be changed to false and related part of XSD should not include minOccurs="0"
      • filters should not be required, then mechanism-provider-filtering-sasl-server-factory must be able to be added without filters attribute - no exception should occur and mechanism-provider-filtering-sasl-server-factory should be stored in configuration

      Exception in server log:

      ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 6) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "elytron"),
    ("mechanism-provider-filtering-sasl-server-factory" => "factory")
]): java.lang.IllegalArgumentException
	at org.jboss.dmr.ModelValue.asList(ModelValue.java:143)
	at org.jboss.dmr.ModelNode.asList(ModelNode.java:1389)
	at org.wildfly.extension.elytron.SaslServerDefinitions$4.installService(SaslServerDefinitions.java:362)
	at org.wildfly.extension.elytron.SaslServerDefinitions$SaslServerAddHandler.performRuntime(SaslServerDefinitions.java:470)
	at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:337)
	at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151)
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:921)
	at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:664)
	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:383)
	at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1364)
	at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:416)
	at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:237)
	at org.wildfly.security.auth.client.PeerIdentity.runAsAll(PeerIdentity.java:431)
	at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:206)
	at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:237)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
	at org.wildfly.security.auth.client.PeerIdentity.runAsAll(PeerIdentity.java:464)
	at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:225)
	at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:185)
	at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157)
	at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
	at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
	at org.jboss.threads.JBossThread.run(JBossThread.java:320)

      This issue is caused by fix of JBEAP-6381.

              rhn-support-ivassile Ilia Vassilev
              olukas Ondrej Lukas (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: