jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Cole (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-480) support AWS signature version 4
Date Thu, 27 Nov 2014 20:44:12 GMT

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

Adrian Cole commented on JCLOUDS-480:
-------------------------------------

I recommend copying or adapting the form signer to create the s3 signature classes. The algo
is basically the same. best luck to whoever does this.

> support AWS signature version 4
> -------------------------------
>
>                 Key: JCLOUDS-480
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-480
>             Project: jclouds
>          Issue Type: New Feature
>          Components: jclouds-core
>            Reporter: Andrew Gaul
>            Priority: Critical
>              Labels: ec2, s3
>             Fix For: 1.8.2, 1.9.0
>
>
> On Mar 15, 2012, Amazon announced a more secure way to sign api requests.
> https://forums.aws.amazon.com/ann.jspa?annID=1398
> New AWS regions, such as Frankfurt, will not support version 2 which jclouds presently
uses:
> http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html
> Eventhough some AWS clones like openstack support both versions, not all do. jclouds
should support both versions.
> This is most important to address for s3 and ec2.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message