You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2018/10/26 05:27:00 UTC

[jira] [Assigned] (ZOOKEEPER-3174) Quorum TLS - support reloading trust/key store

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Han reassigned ZOOKEEPER-3174:
--------------------------------------

    Assignee: Ilya Maykov

> Quorum TLS - support reloading trust/key store
> ----------------------------------------------
>
>                 Key: ZOOKEEPER-3174
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3174
>             Project: ZooKeeper
>          Issue Type: Improvement
>    Affects Versions: 3.6.0, 3.5.5
>            Reporter: Ilya Maykov
>            Assignee: Ilya Maykov
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The Quorum TLS feature recently added in ZOOKEEPER-236 doesn't support reloading a trust/key store from disk when it changes. In an environment where short-lived certificates are used and are refreshed by some background daemon / cron job, this is a problem. Let's support reloading a trust/key store from disk when the file on disk changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)