[
https://issues.apache.org/jira/browse/ARTEMIS-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-4164:
--------------------------------
Description:
In ARTEMIS-400 we added a jmx operation to reload ssl context configuration. It
would make sense to trigger this automatically by default when a change is
detected. We have the file watcher and can register an entry per keystore
reference on acceptor creation.
I think this should be the default but the jmx op has been the way to manually
do this to date. Will make it an option, disabled by default.
h1.
was:
In ARTEMIS-400 we added a jmx operation to reload ssl context configuration. It
would make sense to trigger this automatically by default when a change is
detected. We have the file watcher and can register an entry per keystore
reference on acceptor creation.
I think this should be the default but we can have a autoReload config option
to disable it but it may be sufficient to depend on the file watch period to
disable this feature?
h1.
> Auto reload acceptor SSL keystores on change
> --------------------------------------------
>
> Key: ARTEMIS-4164
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4164
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 2.27.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Labels: Netty, TLS
> Fix For: 2.32.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In ARTEMIS-400 we added a jmx operation to reload ssl context configuration.
> It would make sense to trigger this automatically by default when a change is
> detected. We have the file watcher and can register an entry per keystore
> reference on acceptor creation.
> I think this should be the default but the jmx op has been the way to
> manually do this to date. Will make it an option, disabled by default.
> h1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
