[ https://issues.jboss.org/browse/WFLY-7254?page=com.atlassian.jira.plugin.... ] Ilia Vassilev commented on WFLY-7254: ------------------------------------- [~olukas] You are right that the following command should lead to "outcome" => "failed" so to fix the issue I'll work on changing the code to prevent such commands. Invalid CLI command which should be prevented: {code} /subsystem=elytron/configurable-sasl-server-factory=someFactory:add(sasl-server-factory=global,filters=[{pattern-filter=(.*),predefined-filter=BINDING}]) {code} Valid command: {code} /subsystem=elytron/configurable-sasl-server-factory=someFactory:add(sasl-server-factory=global,filters=[{pattern-filter=(.*), enabling="false"},{predefined-filter=BINDING}]) {code} Configuration after executing it: {code} <configurable-sasl-server-factory name="someFactory" sasl-server-factory="global"> <filters> <filter enabling="false"> <pattern-filter value="(.*)"/> </filter> <filter> <predefined-filter value="BINDING"/> </filter> </filters> </configurable-sasl-server-factory> {code} The above configuration can be correctly loaded when server is started: {code} /subsystem=elytron/configurable-sasl-server-factory=someFactory:read-attribute(name=filters) { "outcome" => "success", "result" => [ { "enabling" => false, "pattern-filter" => "(.*)" }, {"predefined-filter" => "BINDING"} ] } {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)