Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal] Auto Refresh SSL Certs #7375

Closed
niketh opened this issue Mar 28, 2019 · 4 comments
Closed

[Proposal] Auto Refresh SSL Certs #7375

niketh opened this issue Mar 28, 2019 · 4 comments

Comments

@niketh
Copy link
Contributor

niketh commented Mar 28, 2019

Motivation

Whenever SSL certs expire a restart is required to load fresh certs.

Proposed changes

  1. Add property druid.server.https.cert.autoRefresh and druid.server.https.cert.autoRefreshPeriod
  2. Create class CertificateWatcher which watches for changes in druid.server.https.keyStorePath
  3. Once keystore is changed, Jetty does hot reload https://www.eclipse.org/jetty/javadoc/9.4.14.v20181114/org/eclipse/jetty/util/ssl/SslContextFactory.html#reload-java.util.function.Consumer-
@niketh niketh changed the title [Proposal] Auto load SSL Certs [Proposal] Auto Refresh SSL Certs Mar 28, 2019
@drcrallen
Copy link
Contributor

Interesting proposal.

jetty/jetty.project#918 (comment) has some gotchas that will probably need noted on if it impacts here.

There could be other cases where the key store is not on disk though, yes? for example, if a server does on-the-fly decryption out of blob storage to get the key store, then it wouldn't just be a path that needs watched.

In such a scenario, CertificateWatcher would be an interface and not an implementation, so any sort of updates could be handled by an extension.

@gianm
Copy link
Contributor

gianm commented Apr 4, 2019

What is the purpose of druid.server.https.cert.autoRefreshPeriod, if the idea is that a CertificateWatcher would watch for changes and trigger reloads?

In such a scenario, CertificateWatcher would be an interface and not an implementation, so any sort of updates could be handled by an extension.

Definitely sounds useful to have it be an interface, with an implementation in core that simply watches a file.

@stale
Copy link

stale bot commented Jun 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 20, 2019
@stale
Copy link

stale bot commented Jul 4, 2019

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.

@stale stale bot closed this as completed Jul 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants