[
https://issues.apache.org/jira/browse/JAMES-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719403#comment-17719403
]
Wojtek commented on JAMES-3906:
-------------------------------
[~kotto] I was thinking about something simpler like [~btellier] suggested -
simply recreating SSL context - this doesn't require dedicated manager and the
rest IMHO. What's more, it shouldn't probably require recreating/restarting of
the component (i.e. one of the servers like IMAP) - recreating [`encryption`
object|https://github.com/apache/james-project/blob/bd32e30640c3db4ba74e39ba46145f95f18aa46b/server/protocols/protocols-library/src/main/java/org/apache/james/protocols/lib/netty/AbstractConfigurableAsyncServer.java#L100-L100]
by calling [buildSSLContext()
method|https://github.com/apache/james-project/blob/bd32e30640c3db4ba74e39ba46145f95f18aa46b/server/protocols/protocols-library/src/main/java/org/apache/james/protocols/lib/netty/AbstractConfigurableAsyncServer.java#L356-L356]
which should be virtually "instant".
Thought [~btellier] solution may be somewhat cleaner.
> 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/[email protected]/msg16722.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
