[ https://issues.jboss.org/browse/WFLY-7254?page=com.atlassian.jira.plugin.... ] Ondrej Lukas commented on WFLY-7254: ------------------------------------ [~ivassile] In case when CLI commands should look like you mentioned in previous comments then command: {code} /subsystem=elytron/configurable-sasl-server-factory=someFactory:add(sasl-server-factory=global,filters=[{pattern-filter=(.*),predefined-filter=BINDING}]) {code} should lead to "outcome" => "failed". Currently that command results to store both pattern-filter and predefined-filter in dynamic model, but only predefined-filter is stored in configuration. You can try: {code} /subsystem=elytron/configurable-sasl-server-factory=someFactory:add(sasl-server-factory=global,filters=[{pattern-filter=(.*),predefined-filter=BINDING}]) {code} then calling read-attribute operation is successful for both attribute: {code} /subsystem=elytron/configurable-sasl-server-factory=someFactory:read-attribute(name=filters[0].pattern-filter) { "outcome" => "success", "result" => "(.*)" } {code} {code} /subsystem=elytron/configurable-sasl-server-factory=someFactory:read-attribute(name=filters[0].predefined-filter) { "outcome" => "success", "result" => "BINDING" } {code} However after {{reload}} pattern-filter disappears: {code} /subsystem=elytron/configurable-sasl-server-factory=someFactory:read-attribute(name=filters[0].pattern-filter) { "outcome" => "failed", "result" => undefined, "failure-description" => "WFLYCTL0393: Could not resolve attribute expression: 'filters[0].pattern-filter'", "rolled-back" => true } {code} You should also note, that following part of configuration can be correctly loaded when server is started: {code} <configurable-sasl-server-factory name="someFactory" sasl-server-factory="global"> <filters> <filter> <pattern-filter value="(someFilter)"/> <predefined-filter value="BINDING"/> </filter> </filters> </configurable-sasl-server-factory> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)