You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/06/21 18:12:20 UTC

[jira] [Commented] (JENA-475) HTTP Authentication for SPARQL Updates does not actually apply authentication

    [ https://issues.apache.org/jira/browse/JENA-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690429#comment-13690429 ] 

ASF subversion and git services commented on JENA-475:
------------------------------------------------------

Commit 1495492 from [~rvesse]
[ https://svn.apache.org/r1495492 ]

SPARQL Updates created a credentials provider but failed to associate it with the HTTP Client so authentication was not performed (JENA-475)
                
> HTTP Authentication for SPARQL Updates does not actually apply authentication
> -----------------------------------------------------------------------------
>
>                 Key: JENA-475
>                 URL: https://issues.apache.org/jira/browse/JENA-475
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: ARQ
>    Affects Versions: Jena 2.10.1
>            Reporter: Rob Vesse
>            Assignee: Rob Vesse
>             Fix For: Jena 2.10.2
>
>
> A user spotted an error in the logic for applying authentication credentials to SPARQL Updates.  It turns out while we create a CredentialsProvider we fail to associate that with the HTTP Client and so fail to actually peform authentication

--
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