|Re: [jetty-users] TLS ALPN ACME Lets Encrypt challange|
Hi,I am swimming in all directions as well. I get the ALPN TSL extension for switching the protocol and it is working. So, do I need to create a connection factory and connection for the ACME protocol similar to HTTP2?
And where do I manage to create a ACME session for communicating with the certificate provider lets encrypt, within a Jetty handler using the above connection? Or more down the chain in a servlet or the like?
On 29/11/2022 19:16, Simone Bordet wrote:
Hi, On Tue, Nov 29, 2022 at 3:04 PM Info <info@xxxxxxxxxx> wrote:Hi Simone, some premature cheering on my behalf, I was thinking the ALPN processor would do the ACME handling but after re-reading your suggestions it is becoming clear that I need to implement something similar to the HTTP2 Jetty part.I repeatedly said that I think it works out of the box and you should not need to write anything, just configure the list of ALPN protocols.I got the HTTP2 part working and I am getting sessions created and closed, my http test-client reports that h2 is the selected protocol. So now I must create an similar ACME connectionfactory and onOpened add a ACME4J session to the jetty session, or how to combine the Jetty API with the ACME4J api?I'm lost. I don't think you need any of that, it already works out of the box if you configure the list of ALPN protocols.
Back to the top