[
https://issues.apache.org/jira/browse/JAMES-3906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719847#comment-17719847
]
Karsten Otto commented on JAMES-3906:
-------------------------------------
IIRC Encryption is basically a DTO to get the crypto configuration into the
netty pipelines. I assume if you change this to Supplier<Encryption> everywhere
you should be able to update it.
I still do not understand the use case; certificate updates should be quite
rare, since commercial certs are usually valid for a year, and even LetsEncrypt
has 90 days or so. But if it helps you in your deployment, go for it :)
> 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]
