Trevor An invalid certificate exception generally means that the certificate is not trusted (often because it is self-signed) but without seeing a specific error condition and stack trace we can only guess what the actual problem is.
Generally I would not expect it to be a HttpAuthenticator specific problem but again without a stack trace we can only speculate. You can use the debugging support (basically appropriately configuring logging) if you want to see exactly what Apache HTTP Client is doing under the hood: https://jena.apache.org/documentation/query/http-auth.html#debugging-authen tication Trusting a certificate that would otherwise not be trusted is generally a JVM specific task and requires you to either configure the JVM key store on each machine your client runs on appropriately OR do some nasty code hacks that essentially disables SSL certificate verification in your JVM. For example the following SO question shows both approaches: http://stackoverflow.com/questions/2893819/telling-java-to-accept-self-sign ed-ssl-certificate I have some helper scripts that I've used in the past up on BitBucket that can help automate the key store management because it is a little esoteric if you've never had to do it before: https://bitbucket.org/rvesse/java-ssl-helper/overview Note that under some JVMs using this approach may not help (IBM V9 was problematic if memory serves) and you may need to use the code approach instead. See the following code where I've done this in a tool that uses ARQ and HttpAuthenticator's in the past: https://github.com/rvesse/sparql-query-bm/blob/master/cmd/src/main/java/net /sf/sparql/benchmarking/commands/AbstractCommand.java#L444 Rob On 03/02/2015 12:49, "Trevor Donaldson" <[email protected]> wrote: >Is it possible to setup an ssl context using HttpAuthenticator? I am >getting an invalid certificate exception when I try to use DataSetFactory. >I believe this is because the actual call is not using SSL. > >Thanks
