-
Notifications
You must be signed in to change notification settings - Fork 579
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
Reloadable WebServer TLS during runtime #2900
Conversation
a794758
to
b2c677a
Compare
Signed-off-by: David Kral <david.k.kral@oracle.com>
112dc55
to
c18eaea
Compare
Signed-off-by: David Kral <david.k.kral@oracle.com>
Signed-off-by: David Kral <david.k.kral@oracle.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, only a few minor comments. How does that work for requests being processed ? Do they still work off the previously configured TSL context ?
webserver/webserver/src/main/java/io/helidon/webserver/HttpInitializer.java
Outdated
Show resolved
Hide resolved
webserver/webserver/src/main/java/io/helidon/webserver/HttpInitializer.java
Outdated
Show resolved
Hide resolved
webserver/webserver/src/main/java/io/helidon/webserver/NettyWebServer.java
Outdated
Show resolved
Hide resolved
webserver/webserver/src/main/java/io/helidon/webserver/WebServer.java
Outdated
Show resolved
Hide resolved
webserver/webserver/src/main/java/io/helidon/webserver/WebServer.java
Outdated
Show resolved
Hide resolved
Signed-off-by: David Kral <david.k.kral@oracle.com>
Yes, those already connected are still working fine, but the new ones are validated against the new TLS. |
* | ||
* @param tls new TLS configuration | ||
* @param socketName specific named socket name | ||
* @throws IllegalStateException if the new tls is not enabled or currently set tls is null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at the constructor for SockerConfig, we don't keep the WebServerTls
so it's not symetrical :(
How about `if {@link WebServerTls#enabled()} returns {@code false} or if {@link SocketConfiguration#ssl()} returns {@code null}.
We should probably update the ssl configuration for 3.0 @tomas-langer thoughts ?
Signed-off-by: David Kral <david.k.kral@oracle.com>
Signed-off-by: David Kral <david.k.kral@oracle.com>
Reloadable WebServer TLS during runtime Signed-off-by: David Kral <david.k.kral@oracle.com>
Fixes #2863