Backblaze buckets often do not load

[Jstaud]

When opening a connection to backblaze b2, it will often not load the bucket list. It works sometimes and sometimes it doesn't.

[metadaddy]

Hi @Jstaud - when you create an application key that has access to only a single bucket, you can optionally enable the "list all bucket names" permission.

Does the key you're using have this permission? You can check in the Backblaze web console, or using the B2 CLI:

% b2 list-keys --long | grep metadaddy-private | awk '{ print $2, $7 }'
metadaddy-private listAllBucketNames,listBuckets,readBuckets,listFiles,readFiles,shareFiles,writeFiles,deleteFiles,readBucketEncryption,writeBucketEncryption

If you can confirm that this is happening with keys that have listAllBucketNames, then I'll be happy to take a look.

In any case, it might be worth adding code to report to the user that the key does not have the listAllBucketNames permission, to avoid the confusion. What do you think, @dkocher?

Thanks!

[Jstaud]

Hi there,I can confirm that this key was generated with the option to “list all bucket names” permission enabled. It does list all buckets sometimes, but not consistently. I have regenerated new keys to ensure that it’s not just an anomaly with a specific key in Backblaze. Thank you!

[metadaddy]

Thanks, @Jstaud - I'll see if I can reproduce. What version of Cyberduck are you using? Have you used other versions in the past without an issue?

[Jstaud]

I’ll check the version this morning and reply and I’ll check again to see if this is still an issue.

[Jstaud]

Version 8.5.9 (39636)

[Jstaud]

And I think previous versions had the same issue but not as frequent. I just replicated the issue today.

[dkocher]

@metadaddy When connecting with an application key that does not have the listAllBucketNames permission, only the single bucket will be displayed ¹.

Footnotes

1. 894860a ↩

[dkocher]

It does not look like a duplicate of #14527 as this is related to listing buckets and not its contents.

[Jstaud]

This is still an issue and has now rendered the application unusable for my team.