-
Notifications
You must be signed in to change notification settings - Fork 25
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
Reload tls_client_ca_file on SIGHUP #39
Comments
@vishalnayak I will work on this /assign @mahalrs |
@vishalnayak I think we need to update |
@mahalrs were you able to get any progress made on this? Is there anything you need help with, or questions we can answer for you? Let us know if you're blocked. |
Hi folks, it's been a while since we've heard from you regarding this issue. I'm going to go ahead and close it now, but please feel free to re-open if you need. Thanks for your understanding! |
This isn't something mission critical for me, but I don't know why this issue was closed. Is it intentional that this part of the tls config is not reloaded along with the rest? |
Is your feature request related to a problem? Please describe.
Reloading a TCP listener configuration will reload the included tls_cert_file and tls_key_file, but not the tls_client_ca_file.
Describe the solution you'd like
Upon reloading a TCP listener's configuration, reload the tls_client_ca_file if it is configured and enabled.
Describe alternatives you've considered
Restarting vault is an option, but it is convenient to replace certificate pieces while vault is running and allow vault to reload while still serving traffic.
Explain any additional use-cases
Additional context
The text was updated successfully, but these errors were encountered: