[
https://issues.apache.org/jira/browse/JAMES-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720841#comment-17720841
]
Karsten Otto commented on JAMES-3906:
-------------------------------------
If you want to cover the general case then yes. Lets assume you have a WebAdmin
endpoint /reload-certificate or some such, called at the end of the ACME
update. This should send an event to all James instances. All interested
components within can listen for such events to reload their certificates. And
yes, this way you don't have to figure out which components need to be told,
they just subscribe themselves. Seems like a more maintainable architecture to
me.
> Add hot reloading/updating witht restart of the certificate
> -----------------------------------------------------------
>
> Key: JAMES-3906
> URL: https://issues.apache.org/jira/browse/JAMES-3906
> Project: James Server
> Issue Type: New Feature
> Reporter: Wojtek
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It would be great to be able to update the certificate without restarting the
> server, reloading the certificate from the file and/or updating it via REST
> API
>
> Mailing list thread:
> https://www.mail-archive.com/server-user@james.apache.org/msg16722.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
