[
https://issues.apache.org/jira/browse/JENA-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906635#comment-15906635
]
A. Soroka commented on JENA-891:
--------------------------------
This issue looks very different for post 3.1.1 Jena, because we have removed
{{HttpAuthenticator}} in favor of direct use of Commons {{HttpClient}}. I think
the issue is still quite real, just wanted to note the change of context.
> 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
(v6.3.15#6346)
