jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCLOUDS-255) atmos, aws-s3, azure blob signers doesn't support query parameter authentication
Date Sat, 22 Apr 2017 18:56:04 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Gaul resolved JCLOUDS-255.
---------------------------------
       Resolution: Fixed
         Assignee: Andrew Gaul
    Fix Version/s: 2.1.0

Azure, GCS, S3, and Swift now use query parameters for signed URLs.  Atmos and B2 do not support
this mechanism.

> 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
>            Assignee: Andrew Gaul
>              Labels: atmos, azureblob, s3
>             Fix For: 2.1.0
>
>
> 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
(v6.3.15#6346)

Mime
View raw message