-
Notifications
You must be signed in to change notification settings - Fork 284
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
https server with short lived ssl credentials #603
Comments
Node.js has no official support for that (yet) but see nodejs/node#4464 (comment) for a workaround. |
Thank You |
4 tasks
cjihrig
added a commit
to cjihrig/node
that referenced
this issue
Oct 21, 2018
This commit adds a setSecureContext() method to TLS servers. In order to maintain backwards compatibility, the method takes the options needed to create a new SecureContext, rather than an instance of SecureContext. Fixes: nodejs#4464 Refs: nodejs#10349 Refs: nodejs/help#603 Refs: nodejs#15115 PR-URL: nodejs#23644 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
jasnell
pushed a commit
to nodejs/node
that referenced
this issue
Oct 21, 2018
This commit adds a setSecureContext() method to TLS servers. In order to maintain backwards compatibility, the method takes the options needed to create a new SecureContext, rather than an instance of SecureContext. Fixes: #4464 Refs: #10349 Refs: nodejs/help#603 Refs: #15115 PR-URL: #23644 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
sam-github
pushed a commit
to sam-github/node
that referenced
this issue
Apr 29, 2019
This commit adds a setSecureContext() method to TLS servers. In order to maintain backwards compatibility, the method takes the options needed to create a new SecureContext, rather than an instance of SecureContext. Fixes: nodejs#4464 Refs: nodejs#10349 Refs: nodejs/help#603 Refs: nodejs#15115 PR-URL: nodejs#23644 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have ssl credentials which are short lived (age is few hours) and are keep getting refreshed on the box
If there anyway where a running server can reload the certificates without restarting.
In Java-Jetty world something like this can be done using reload.
Is there anything similar in nodejs?
AFAIK, the only way to do this is to restart the server
We figured we can do sort of dynamic reload if we are running in cluster mode. The master can watch the certificate files and
fork
a new worker andkill
the existing workers gracefully on a cert updateBut I am not able to figure something on a standalone mode which can be graceful.
The text was updated successfully, but these errors were encountered: