[
https://issues.apache.org/jira/browse/JENA-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617778#comment-13617778
]
Rob Vesse commented on JENA-428:
--------------------------------
Have this work done and committed, my changes use HttpContext as the way to
carry the auth parameters into HttpOp
At the update processor level remote update processors now respect the same
service context authentication settings that QueryEngineHTTP and SERVICE
clauses respect. There is also a setAuthentication() method on
UpdateProcessRemoteBase that users can use to set auth credentials directly
where necessary.
> Remote updates do not respect srv:serviceContext
> ------------------------------------------------
>
> Key: JENA-428
> URL: https://issues.apache.org/jira/browse/JENA-428
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 2.10.0
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Labels: authentication, sparql, update
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> This is a follow on issue prompted by JENA-405, that issue requested support
> for respecting the service context for remote SPARQL queries which allowed
> for setting certain parameters in a centralized place rather than every time
> you wanted to access a service.
> It seems reasonable that we should do the same for updates but having looked
> at the code there appears to be no existing way to inject authentication
> parameters for updates. This is a lacking feature since it would seem more
> likely that credentials would be needed for updates than queries.
--
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
