You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Sören Brunk (JIRA)" <ji...@apache.org> on 2012/11/15 18:30:13 UTC

[jira] [Created] (JENA-348) Support HTTP auth for SPARQL Update requests

Sören Brunk created JENA-348:
--------------------------------

             Summary: 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
            Priority: Minor


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

[jira] [Updated] (JENA-348) Support HTTP auth for SPARQL Update requests

Posted by "Sören Brunk (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JENA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sören Brunk updated JENA-348:
-----------------------------

    Attachment: jena-348.patch

Patch that enables adding an HttpContext to UpdateProcessRemote and UpdateProcessRemoteForm that will be used when executing the update request.

It doesn't change any existing method signatures, only adds a few overloaded methods.
In addition, for now it only extends the methods of HttpOp that are used by UpdateProcessRemote and UpdateProcessRemoteForm to support HttpContext.

I've successfully tested it for HTTP Basic auth with a SPARQL Endpoint.
                
> 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
>            Priority: Minor
>         Attachments: jena-348.patch
>
>
> 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

[jira] [Commented] (JENA-348) Support HTTP auth for SPARQL Update requests

Posted by "Claude Warren (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JENA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498655#comment-13498655 ] 

Claude Warren commented on JENA-348:
------------------------------------

I think that a better solution might be to create an HttpContext that would be used for all calls.  This would allow for other authentication mechanisms like OAuth or OpenID. 
                
> 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
>            Priority: Minor
>
> 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