[jira] [Commented] (JCLOUDS-1519) Support for Backblaze application keys
[ https://issues.apache.org/jira/browse/JCLOUDS-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818764#comment-17818764 ] ASF subversion and git services commented on JCLOUDS-1519: -- Commit 41d842d449e125411709613e27ca01c8fc5c4a4f in jclouds's branch refs/heads/dependabot/maven/project/org.testng-testng-7.5.1 from davidsenk [ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=41d842d449 ] JCLOUDS-1519: Fix the authorization error with b2 application keys > 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 >Assignee: Andrew Gaul >Priority: Major > Fix For: 2.6.0 > > > 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.20.10#820010)
[jira] [Commented] (JCLOUDS-1519) Support for Backblaze application keys
[ https://issues.apache.org/jira/browse/JCLOUDS-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818322#comment-17818322 ] ASF subversion and git services commented on JCLOUDS-1519: -- Commit 41d842d449e125411709613e27ca01c8fc5c4a4f in jclouds's branch refs/heads/master from davidsenk [ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=41d842d449 ] JCLOUDS-1519: Fix the authorization error with b2 application keys > 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.20.10#820010)
[jira] [Commented] (JCLOUDS-1519) Support for Backblaze application keys
[ https://issues.apache.org/jira/browse/JCLOUDS-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17814373#comment-17814373 ] David Senk commented on JCLOUDS-1519: - This is fixed with PR # 190 [https://github.com/apache/jclouds/pull/190] > 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.20.10#820010)
