[
https://issues.apache.org/jira/browse/JENA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558692#comment-13558692
]
Rob Vesse commented on JENA-348:
--------------------------------
The main problems look to be that HttpOp was in the org.openjena package so has
now moved to org.apache.jena hence why the patch to HttpOp cannot be applied
and the patches to the other files fail because the other files have
conflicting changes which address the package renames
I can probably manually apply this given time but if Soren can regenerate the
patch against the latest codebase that would be easiest
> Support HTTP auth for SPARQL Update requests
> --------------------------------------------
>
> Key: JENA-348
> URL: https://issues.apache.org/jira/browse/JENA-348
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: ARQ 2.9.4
> Reporter: Sören Brunk
> Assignee: Rob Vesse
> Priority: Minor
> Fix For: Jena 2.10.0
>
> Attachments: jena-348-1.patch, jena-348.patch, UpdateAuthExample.java
>
>
> ARQ supports HTTP Basic Authentication for read queries
> (setBasicAuthentication() in QueryEngineHTTP).
> I can't find authentication support for SPARQL Update though. The responsible
> class UpdateProcessRemote uses HttpOp as an abstraction, and HttpOp in turn
> encapsulates HttpClient from Apache HTTP Components.
> So I guess a way to go would be to extend HttpOp to support auth or to expose
> the HttpClient object in order to set auth options as described in [1].
> I'm happy to help if I can get some hints about the preferred way to include
> auth support.
> [1]
> http://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
