[
https://issues.apache.org/jira/browse/JENA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690654#comment-16690654
]
Andy Seaborne commented on JENA-891:
------------------------------------
Is this still a live issue?
We have placed responsibility on to the setup of {{HttpClient}}. This is
probably inevitable because there are such a range
Library
[LibSec|https://github.com/apache/jena/blob/master/jena-rdfconnection/src/main/java/org/apache/jena/rdfconnection/LibSec.java]
has some helper code for {{HttpClient}} setup.
> Add assembler support for HTTP Authenticator
> --------------------------------------------
>
> Key: JENA-891
> URL: https://issues.apache.org/jira/browse/JENA-891
> Project: Apache Jena
> Issue Type: Bug
> Affects Versions: Jena 2.11.0
> Reporter: Rob Vesse
> Priority: Minor
>
> This
> [question|http://stackoverflow.com/questions/28812206/federated-query-with-secured-sparql-endpoint/28829913#28829913]
> made my realise that the solution there only works for simple authentication
> scenarios. If users wanted to take advantage of more complex authentication
> strategies then they would have no way of doing that via assembler.
> So we need the following:
> * Assembler support for {{HttpAuthenticator}} instances
> * Ability to specify a {{HttpAuthenticator}} in a service context as opposed
> to basic auth credentials
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
