[
https://issues.jboss.org/browse/WFCORE-1606?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-1606:
------------------------------------------
When looking at this we should examine the possibility of actually supporting
allow-resource-service-restart=true, as opposed to correcting the metadata. But this all
ties in to the elytron migration as well, i.e. we shouldn't change the behavior of
security-realm in a way that will be different from what the elytron subsystem stuff
supports.
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)