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 Sat, 22 Apr 2017 18:15:04 GMT

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

ASF subversion and git services commented on JCLOUDS-255:

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

JCLOUDS-255: JCLOUDS-1109: Azure signed URLs expiration

This commit also changes signed URLs from header-based to query

> 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
>              Labels: atmos, azureblob, s3
> 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