[
https://issues.jboss.org/browse/WFCORE-1606?page=com.atlassian.jira.plugi...
]
Brian Stansberry reassigned WFCORE-1606:
----------------------------------------
Assignee: ehsavoie Hugonnet
Emmanuel, please have a look at this, starting off with discussing a bit with
[~dlofthouse]. I'm quite fine with fixing this by simply correcting the metadata, and
not actual supporting allow-resource-service-restart=true. We should only go beyond that
if:
1) The elytron replacements for these legacy security-realm resources will support
allow-resource-service-restart=true *in core 3.0.0 / WF 11*.
2) Darran is up for reviewing a patch to add the support.
Otherwise let's just fix the metadata.
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, Security
Affects Versions: 2.0.10.Final
Reporter: Ondrej Lukas
Assignee: ehsavoie Hugonnet
Fix For: 3.0.0.Beta1
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
(v7.2.2#72004)