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/20 23:49:34 UTC
[jira] [Comment Edited] (JCLOUDS-480) support AWS signature version
4
[ https://issues.apache.org/jira/browse/JCLOUDS-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14217527#comment-14217527 ]
Adrian Cole edited comment on JCLOUDS-480 at 11/20/14 10:49 PM:
----------------------------------------------------------------
implementation complete https://github.com/jclouds/jclouds/pull/610
was (Author: adriancole):
started on form signing variant https://github.com/jclouds/jclouds/pull/610
> 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)