[
https://issues.jboss.org/browse/WFCORE-1606?page=com.atlassian.jira.plugi...
]
Brian Stansberry edited comment on WFCORE-1606 at 6/23/16 1:37 PM:
-------------------------------------------------------------------
[~iweiss]
https://github.com/wildfly/wildfly-core/blob/master/domain-management/src...
is wrong. SecurityRealmChildRemoveHandler does not support the
allow-resource-service-restart=true header.
I believe this is a common mistake in the uses of SecurityRealmParentRestartHandler; the
first other one I checked had the same problem.
was (Author: brian.stansberry):
[~iweiss]
https://github.com/wildfly/wildfly-core/blob/master/domain-management/src...
is wrong. SecurityRealmChildRemoveHandler does not support the
{allow-resource-service-restart=true} header.
I believe this is a common mistake in the uses of SecurityRealmParentRestartHandler; the
first other one I checked had the same problem.
Server reload is needed for modified security-realm even if
{allow-resource-service-restart=true} is used
---------------------------------------------------------------------------------------------------------
Key: WFCORE-1606
URL:
https://issues.jboss.org/browse/WFCORE-1606
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.0.10.Final
Reporter: Ondrej Lukas
Assignee: Brian Stansberry
When security-realm, which is set as http-interface security-realm in
management-interfaces, is modified and operation used
{allow-resource-service-restart=true} header then server is NOT in reload-required state
but modified security realm does not work correctly until server is manually reloaded.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)