You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JettyServletWebserverFactory sets up SSL connector by creating an SslServerCustomizer. This customizer's 'customize' method encapsulates the SslContextFactory instance. So we do not have access to this instance to reload the SSL certificates using the Jetty 'hot reload' (jetty/jetty.project#918)
It is also not easy to use this SslServerCustomizer to create another HTTPS connector. For example, we are setting up two HTTPS endpoints - one with 1-way SSL and the other with 2-way SSL. This requires code duplication today.
The text was updated successfully, but these errors were encountered:
SslServerCustomizer is package-private and is intended for internal use only. Rather than trying to use it, I would recommend using Jetty's API's directly. For example, you can get from a Jetty Server to the SslContextFactory of each HTTPS-capable connector with code like this:
In Spring Boot, you can access an instance of the Server in a few ways. One way is via a JettyServerCustomizer bean, another is via WebServerApplicationContext.getWebServer() and ((JettyWebServer)webServer).getServer().
Alternatively, if you are already programmatically configuring the second HTTPS-capable connector, you may want to configure the first programmatically as well. This would allow you to create the SslContextFactory and hold a reference to it, rather than having to retrieve it from the Connector that Boot has created for you.
JettyServletWebserverFactory sets up SSL connector by creating an SslServerCustomizer. This customizer's 'customize' method encapsulates the SslContextFactory instance. So we do not have access to this instance to reload the SSL certificates using the Jetty 'hot reload' (jetty/jetty.project#918)
It is also not easy to use this SslServerCustomizer to create another HTTPS connector. For example, we are setting up two HTTPS endpoints - one with 1-way SSL and the other with 2-way SSL. This requires code duplication today.
The text was updated successfully, but these errors were encountered: