You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Roded Bahat (Jira)" <ji...@apache.org> on 2019/08/21 12:22:00 UTC

[jira] [Created] (JCLOUDS-1511) Support non-AWS S3 with V4 signatures

Roded Bahat created JCLOUDS-1511:
------------------------------------

             Summary: Support non-AWS S3 with V4 signatures
                 Key: JCLOUDS-1511
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1511
             Project: jclouds
          Issue Type: Improvement
            Reporter: Roded Bahat


We'd like to use V4 signatures with the S3 API for some non-AWS object storage vendors.
 We've found several mentions of this requirement in other issues with the recommendation of creating a new Guice module which binds {{RequestAuthorizeSignature}} to {{RequestAuthorizeSignatureV4}}. This does indeed seems to work properly.

Is this still the recommend approach? Or is there a more ideal solution for JClouds which we could consider creating a PR for? For example, allow changing the bound {{RequestAuthorizeSignature}} via a configuration property.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)