| Re: [jetty-users] Jetty 10 SSL configuration |
|
Thank you Joakim for the great information. I do happen to be using Java 11 on RHEL 8 because the Shibboleth IDP application requires it. So, I am not sure what
I will have to look out for, since I am using Java 11. Thanks Vince From: jetty-users <jetty-users-bounces@xxxxxxxxxxx>
On Behalf Of Joakim Erdfelt Hoo boy, this is a HUGE topic, and is not suitable for email. The basics, For server side TLS (this is what it's called now, SSL is dead, long live TLS), you'll need ... * A Java keystore (required) * A Java truststore (optional, you don't have to create one, you can even just use the built in defaults) * A Jetty configuration to find the keystore file (this is the SslContextFactory.Server) * A Jetty configuration for your connector (the thing that accepts connections) * A Jetty configuration to find the specific details in the keystore that you want to use for that connector. For the Java keystore, you'll want PKCS12 format, and the techniques to get your certificates into that keystore are documented all over the internet. Just pick documentation that suits your version of Java and OS best. (so don't pick documentation talking about Java 7 on Windows if you are using Java 11 on Linux, as the tools you will use will be different). Once you have this keystore file setup with your certificates you'll need to setup the configurations on Jetty side (listed above). You'll need to know things like the keystore passwords and any aliases within the keystore you might have configured, etc. Then you'll optionally have to setup permissions on your OS to allow Jetty to bind to port 443. (do yourself a favor and use 8443 while testing, make sure it works on that port first, then worry about the OS permissions issue when you switch
to port 443). Joakim Erdfelt /
joakim@xxxxxxxxxxx On Thu, May 12, 2022 at 4:17 PM Esquivel, Vince <Esquivelv@xxxxxxx> wrote:
|