[GRADLE-3226] S3 Maven backed repositories should support AWS Signature Version 4 Created: 20/Jan/15 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | René Gröschke (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Description |
|
The AWS S3 support in Gradle should support AWS Signature Version 4 as described in http://docs.aws.amazon.com/general/latest/gr/signature-version-4.html The latest release of the jets3t library doesn't support this, but basic support is added to master waiting to be released: https://bitbucket.org/jmurty/jets3t/issue/183/support-for-aws-signature-version-4 The main motivation to support this kind of authentication comes from the fact that some aws regions are exclusively supporting this kind of authentication (central europe) |
| Comments |
| Comment by Benjamin Muschko [ 15/Nov/16 ] |
|
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
| Comment by Benjamin Muschko [ 10/Feb/17 ] |
|
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |