[ https://issues.jboss.org/browse/WFCORE-3421?page=com.atlassian.jira.plugi... ] Martin Choma updated WFCORE-3421: --------------------------------- Description: If outflow-anonymous is set to false then there is no need for outflow-security-domains as the default configuration shows clearly. So {noformat} /subsystem=elytron/security-domain=ApplicationDomain:add(default-realm=ApplicationRealm,outflow-anonymous=false,realms=[{realm=ApplicationRealm,role-decoder=groups-to-roles}]) {noformat} should work like {noformat} /subsystem=elytron/security-domain=ApplicationDomain:add(default-realm=ApplicationRealm,realms=[{realm=ApplicationRealm,role-decoder=groups-to-roles}]) {noformat} A custom validation code is required instead of relying on the setRequires of SimpleAttributeDefinition was: If outflow-anonymous is set to false then there is no need for outflow-security-domains as the default configuration shows clearly. So /subsystem=elytron/security-domain=ApplicationDomain:add(default-realm=ApplicationRealm,outflow-anonymous=false,realms=[{realm=ApplicationRealm,role-decoder=groups-to-roles}]) should work like /subsystem=elytron/security-domain=ApplicationDomain:add(default-realm=ApplicationRealm,realms=[{realm=ApplicationRealm,role-decoder=groups-to-roles}]) A custom validation code is required instead of relying on the setRequires of SimpleAttributeDefinition -- This message was sent by Atlassian JIRA (v7.5.0#75005)