[
https://issues.jboss.org/browse/WFLY-6573?page=com.atlassian.jira.plugin....
]
Brad Maxwell edited comment on WFLY-6573 at 10/26/18 1:47 PM:
--------------------------------------------------------------
At a simplistic level, this is like changing a system property at runtime, but in reality
everything that is configured with these properties has to be restarted, such as
datasources, ldap, etc... Which would not be recommended to do at runtime when these
resources are likely being actively used and changing without restart where it basically
restarts everything using it seems like it does not gain that much.
Datasources and ldap configuration are a couple of areas which would need to be
investigated to restart and anything that uses those.
was (Author: bmaxwell):
At a simplistic level, this is like changing a system property at runtime, but in reality
everything that is configured with these properties has to be restarted, such as
datasources, ldap, etc... Which would not be recommended to do at runtime when these
resources are likely being actively used and changing without restart where it basically
restarts everything using it seems like it does not gain that much.
Allow Vault encrypted strings to be updated without a restart
-------------------------------------------------------------
Key: WFLY-6573
URL:
https://issues.jboss.org/browse/WFLY-6573
Project: WildFly
Issue Type: Feature Request
Components: Security
Affects Versions: 10.0.0.Final
Reporter: Brad Maxwell
Priority: Major
When a new vault string is created the affected servers in the domain have to be
restarted before the encrypted value is applied. This makes it difficult to test a new
configuration in CLI.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)