>
> Does the reload on keystore change work with "Lets Encrypt!"?
Yes. I use deploy hook for certbot.
/etc/letsencrypt/renewal-hooks/deploy/fuseki_cert_update.sh:
#!/bin/bash
cert_path=/etc/letsencrypt/live/domain
openssl pkcs12 -export -in $cert_path/fullchain.pem -inkey
$cert_path/privkey.pem -out /etc/fuseki/keystore.p12 -name jetty -password
file:/etc/fuseki/keystore_password.txt
ср, 16 февр. 2022 г. в 20:35, Andy Seaborne <a...@apache.org>:
> Hi Vladimir,
>
> Thanks for the information! It is good to know what things still work.
>
> Does the reload on keystore change work with "Lets Encrypt!"?
>
> I've created JENA-2284 [1] to make sure the example gets updated.
>
>
> Fuseki/Main has a special support
>
> --https=CONF
> https certificate access details.
> JSON file { "cert":FILE , "passwd"; SECRET }
>
> but this isn't trying to be a complete solution.
>
> Eventually, (no timescale - several things to get sorted out first), the
> standalong fuseki-server will be that code.
>
> Andy
>
> [1] https://issues.apache.org/jira/browse/JENA-2284
>
> On 16/02/2022 12:32, Vladimir Shestakov wrote:
> > Hello!
> > Successfully run Fuseki 4.4.0 (Jetty 10.0.7) with option "--jetty-config
> > fuseki-jetty-https.xml" on this config (see below).
> > For Fuseki 4.2.0 (Jetty 10.0.6) it works too.
> > It based on config from examples (
> >
> https://github.com/apache/jena/blob/main/jena-fuseki2/examples/fuseki-jetty-https.xml
> )
> > and updated: removed useless <Property>, added option to reload on
> keystore
> > change, optimized a little.
> >
> > Vladimir
> >
> > fuseki-jetty-https.xml:
>
