-
Bug
-
Resolution: Done
-
Blocker
-
2.9.4.Final
-
None
User see following HTTP API error:
Unexpected HTTP response: 500 Request { "name" => "TestDomain", "outflow-anonymous" => false, "outflow-security-domains" => undefined, "permission-mapper" => undefined, "post-realm-principal-transformer" => undefined, "pre-realm-principal-transformer" => undefined, "principal-decoder" => undefined, "realm-mapper" => undefined, "role-mapper" => undefined, "security-event-listener" => undefined, "trusted-security-domains" => undefined, "realms" => [{ "realm" => "local", "principal-transformer" => undefined, "role-decoder" => undefined, "role-mapper" => undefined }], "default-realm" => "local", "address" => [ ("subsystem" => "elytron"), ("security-domain" => "TestDomain") ], "operation" => "add" } Response Internal Server Error { "outcome" => "failed", "failure-description" => "WFLYCTL0380: Attribute 'outflow-security-domains' needs to be set or passed before attribute 'outflow-anonymous' can be correctly set", "rolled-back" => true }
The problem is caused by web console setting outflow-anonymous attribute to the default value even without user touching this attribute. But outflow-anonymous attribute if not let undefined requires outflow-security-domains to be set.
- clones
-
JBEAP-9779 Not possible to create security domain in Elytron subsystem configuration in web console without outflow-security-domains attribute specified
- Closed