[jira] [Commented] (JCLOUDS-1519) Support for Backblaze application keys

["Elton Carneiro (Jira)" <ji...@apache.org>]

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

Elton Carneiro commented on JCLOUDS-1519:
-----------------------------------------

Please see this issue for suggestions on how to fix this: [https://github.com/gaul/s3proxy/issues/298]

> Support for Backblaze application keys
> --------------------------------------
>
>                 Key: JCLOUDS-1519
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1519
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 2.1.2
>            Reporter: Elton Carneiro
>            Priority: Major
>
> The current implementation of the B2 API in JClouds only supports Master Keys and not application keys. 
> When using the Master Key, the Key ID and the Account ID are the same. However, when using Application Keys, the Key ID of the application key is not the same as the account ID. The account ID is what is needed to make certain calls such as bucket operations.
> The response of the [b2_authorize_account|https://www.backblaze.com/b2/docs/b2_authorize_account.html] contains the account ID.
> If you look at the [b2_list_buckets|https://www.backblaze.com/b2/docs/b2_list_buckets.html] endpoint, it takes in an account ID. This Account ID is returned in the authorize call.
> Looking at the source code, It seems that the account ID is being pulled from the credentials that the user entered versus the response from the authorize call.
> This issue prevents users from using Application keys when using JClouds. 
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)