[
https://issues.apache.org/jira/browse/JCLOUDS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222023#comment-14222023
]
ASF subversion and git services commented on JCLOUDS-480:
---------------------------------------------------------
Commit 243b96798a7f8c17730c5d1f67dbc4dc782b2285 in jclouds's branch
refs/heads/1.8.x from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=243b967 ]
JCLOUDS-480 support version 4 signatures for aws-ec2.
> 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
> Assignee: Adrian Cole
> 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)
