You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Adrian Cole (JIRA)" <ji...@apache.org> on 2014/11/18 16:59:34 UTC
[jira] [Commented] (JCLOUDS-480) support AWS signature version 4
for S3
[ https://issues.apache.org/jira/browse/JCLOUDS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216350#comment-14216350 ]
Adrian Cole commented on JCLOUDS-480:
-------------------------------------
I'll help with this, as it is breaking a bunch of folks. We already have means to select auth mechanism in keystone and oauth. We can make the default the old school and bump aws-* to new school.
> 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
> Assignee: Adrian Cole
> Labels: s3
> Fix For: 1.8.2, 1.9.0
>
>
> 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)