[
https://issues.apache.org/jira/browse/JAMES-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719815#comment-17719815
]
Matthieu Baechler commented on JAMES-3906:
------------------------------------------
Hi there,
We worked a bit on that topic yesterday with [~jeantil] and found that we can
probably update the current certificate without restarting anything (it would
prevent from stopping ongoing connections).
For every new connection, `AbstractSSLAwareChannelPipelineFactory` creates a
new sslHandler, so if we can update the SSLContext into `Encryption`, a new
certificate would be picked for new connections.
> 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
