[ https://issues.jboss.org/browse/WFLY-1838?page=com.atlassian.jira.plugin.... ] Heiko Braun updated WFLY-1838: ------------------------------ Description: When I look at datasources for example, I can see a difference between :read-resource-description(access-control=true) and the output of :read-resource(){roles=monitor}. The first doesn't contain constraints for "security-domain", but the later indicates them as being filtered (access-control response header). First question: Is this a bug? Second and more general question: Will all filtered attributes be presented as "read=false" & "write=false"? was: When I look at datasources for example, I can see a difference between :read-resource-description(access-control=true) and the output of :read-resource(){roles=monitor}. The first doesn't contain constraints for "security-domain", but the later indicates them as being filtered (access-control response header). First question: Is this a bug? Second and more general question: Will all filtered attributes be indicated as "read=false" & "write=false"? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira