[JCLOUDS-1519] Support for Backblaze application keys

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.2
• Fix Version/s: 2.6.0
• Component/s: jclouds-blobstore
• Assignee: Andrew Gaul
• Reporter: Elton Carneiro
• Created: 08/Oct/19 20:17
• Updated: 20/Feb/24 11:21
• Resolved: 19/Feb/24 12:37

Description

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 contains the account ID.

If you look at the b2_list_buckets 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.