]
Martin Choma commented on WFCORE-3421:
--------------------------------------
Sorry, I thought edit of my previous comment invalidates your comment. So I wanted hold
conversation consistent.
Deleted Darran's comment:
{noformat}
Do we have any examples where setting an attribute to it's default value does mean
that it's required attribute must also be defined?
{noformat}
Incorrect usage of requires for defining the relationship between
outflow-anonymous and outflow-security-domains
----------------------------------------------------------------------------------------------------------------
Key: WFCORE-3421
URL:
https://issues.jboss.org/browse/WFCORE-3421
Project: WildFly Core
Issue Type: Bug
Components: Security
Affects Versions: 4.0.0.Alpha2
Reporter: ehsavoie Hugonnet
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