jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-255) atmos, aws-s3, azure blob signers doesn't support query parameter authentication
Date Wed, 19 Apr 2017 07:55:42 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974266#comment-15974266

ASF subversion and git services commented on JCLOUDS-255:

Commit db00f679ef32831bc65bcea02ecb05bc5330a5b9 in jclouds's branch refs/heads/master from
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=db00f67 ]

JCLOUDS-255: Consistently use query string auth

Fixes regressions introduced in

> atmos, aws-s3, azure blob signers doesn't support query parameter authentication
> --------------------------------------------------------------------------------
>                 Key: JCLOUDS-255
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-255
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 1.6.2
>            Reporter: Kevin Krouse
>            Priority: Minor
>              Labels: atmos, azureblob
> Some blob store providers allow using signed requests in two forms: either with an Authorization
header or with query parameters.  Using the query parameter form of the signed request is
necessary for clients that don't support adding a header or for returning a redirect where
the Authorization header would be removed.
> The jclouds atmos, aws-s3, and azure implementations generate signed requests only with
the Authorization header, while cloudfiles-us, hpcloud-objectstorage use query parameters.
 Ideally the BlobRequestSigner interface would allow the user to decide which form of signed
request to create.

This message was sent by Atlassian JIRA

View raw message