]
Jan Kalina edited comment on WFLY-7501 at 11/9/16 12:21 PM:
------------------------------------------------------------
I think the bug actually is that domain A can have A in trusted domains. (That A doesnt
exist yet is not problem)
was (Author: honza889):
I think the bug actually is that domain A can have A in trusted domains.
Security domain can have itself in
"trusted-security-domains"
-------------------------------------------------------------
Key: WFLY-7501
URL:
https://issues.jboss.org/browse/WFLY-7501
Project: WildFly
Issue Type: Bug
Components: Security
Reporter: Hynek Švábek
Assignee: Jan Kalina
Security-domain trusted-security-domains attribute has confusing behaviour. I can define
there security domain which doesn't exist yet (It is being created right now).
*Steps to reproduce*
{code}
/subsystem=elytron/filesystem-realm=realm1:add(relative-to=jboss.server.config.dir,
path=tmp.prop)
{code}
{code}
/subsystem=elytron/security-domain=secDomain888:add(realms=[{realm=realm1}],
default-realm=realm1, trusted-security-domains=[secDomain888])
{code}