As I mentioned, I have Fuseki running using SSL with a valid certificate. However, when I try to access the site remotely, using the Jena libs, I get the exception below.
Firefox shows that the endpoint (via the admin app) is a valid Digicert certificate. Is there something missing in the Jena API handshake? org.apache.jena.atlas.web.HttpException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at org.apache.jena.riot.web.HttpOp.exec(HttpOp.java:1125) at org.apache.jena.riot.web.HttpOp.execHttpHead(HttpOp.java:1039) at org.apache.jena.web.DatasetGraphAccessorHTTP.doHead(DatasetGraphAccessorHTTP.java:156) at org.apache.jena.web.DatasetGraphAccessorHTTP.httpHead(DatasetGraphAccessorHTTP.java:150) at org.apache.jena.web.DatasetAdapter.containsModel(DatasetAdapter.java:56) ... ... .... ... ... On Fri, Sep 11, 2015 at 10:54 PM, Jason Levitt <[email protected]> wrote: > Andy, > > When do you officially plan to release Fuseki 2.3.1 with Netty updated? > > Cheers, > > J > > On Sat, Sep 5, 2015 at 3:12 PM, Andy Seaborne <[email protected]> wrote: >> After exchanging intact XML files offlist, Jason and I managed to get a >> working Jetty configuration for HTTP+HTTPS to work with Fuseki after the >> updates to Jetty 9.3.3: >> >> This should be taken as an example, not the definitive setup. >> >> https://gist.github.com/afs/63a80512cdc55caf77d0 >> >> Improvements and verification very welcome. >> >> Andy
