Backblaze B2 Application Keys

implemented
backblaze-b2

#1

BackBlaze’s B2 (finally) supports separate keys for separate applications. See Application Keys and Should we create a new Backblaze account for each app we use Cloud Storage for since we only get one application key? : backblaze

I’ve been unable to figure out how to use them with duplicacy. The “global” account id and key work fine, but I get:

URL request 'https://api000.backblazeb2.com/b2api/v1/b2_list_buckets' returned status code 400

when I try to use the application specific key and id. It would be great to be able to use these, it would keep potential damage from key compromise much more contained.

Thanks for your help,
Robert


Backing Up Large Datasets to Both Local and Backblaze B2 Destinations Using Duplicacy CLI on Linux
Unable to init b2 bucket on FreeBSD
#2

Right, i started with duplicacy just today and couldn’t figure out for a 1st few times what was wrong before actually trying out the master key which worked. The application-keys result in authentication failure.


#3

This is an issue with the b2_list_buckets api call – it should have returned the bucket(s) that the application key can access. I just received a message from Backblaze saying that this will be fixed by Aug 16th. If you can’t wait then you can try to build your own binary from the PR contributed by bekriebel: b2client: Add the ability to use a restricted Application ID by bekriebel · Pull Request #475 · gilbertchen/duplicacy · GitHub


#4

Well, it’s August 22. Where can we follow this modification of the B2 API, scheduled for the 16th? Do you know if it has already been implemented? Is it necessary to rebuild Duplicacy or is it simply a “B2 side” modification?


#5

This should be fixed by Get accountID from b2_authorize_account and supply it to b2_list_buckets · gilbertchen/duplicacy@674d35e · GitHub

I thought this was supposed to be a “B2 side” modification only but it turns out that the account id is still needed by b2_list_buckets when an application key is used.


#6

This topic was automatically closed after 22 days. New replies are no longer allowed.