[
https://issues.apache.org/jira/browse/JCLOUDS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181740#comment-14181740
]
Andrew Gaul commented on JCLOUDS-480:
-------------------------------------
[~diwaker] The v2 authorization header has a prefix {{AWS}} while v4 has
{{AWS4-HMAC-SHA256}}. The client sending one or the other determines what the
server should validate; there is no fallback provision for sending multiple
Authorization headers.
I anticipate that jclouds would default the aws-s3 provider to v4 and the
generic s3 to v2. It would be nice to allow generic s3 to opt-in to the v4
mode as well. Note that we have a v4 signer already in the glacier provider
but need to reparent it to sts.
> support AWS signature version 4 for S3
> --------------------------------------
>
> Key: JCLOUDS-480
> URL: https://issues.apache.org/jira/browse/JCLOUDS-480
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-blobstore
> Reporter: Andrew Gaul
> Labels: s3
>
> New AWS regions will not support version 2 which jclouds presently uses:
> http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html
> jclouds should support both versions since some S3 clones do not support
> version 4.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
