Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

B2 App Key Auth #12

Open
joelmacklow opened this issue May 3, 2019 · 2 comments
Open

B2 App Key Auth #12

joelmacklow opened this issue May 3, 2019 · 2 comments

Comments

@joelmacklow
Copy link

joelmacklow commented May 3, 2019

Versions

  • Cloud Media Offloader: 0.8.1
  • WordPress: 5.1
  • PHP: 7.3
  • Hosting Environment (ie, Windows, Linux): Linux

Description of Issue/Request

Hi Daniel. Just taking a look at using this plugin that you've written. I'm far from being a coder, but would like to help out if I can :)

I've tried to use this with a B2 app key instead of the master key as I want to be able to protect the master key as this plugin will be installed on a client WP site using a bucket in our account.

When I enter the app key and save the settings, no buckets are in the list, even though the app key has the list buckets permission. I have limited the app key to a single bucket. I should mention that it does work fine if I do use the master key.

Is there something I need to change for this to work or can this only work using the master key?

@phaberest
Copy link

I'm afraid this is a pretty common issue, this repo might be using the old api that do not recognise bucket specific key but instead they only allow the global api key. I had the same issue with the cli script I use to upload my weekly backups.

@hxrsmurf
Copy link

I'm very new at coding and wanted to have a way to have backblaze as my backend storage instead of local storage or S3. Here's my version of a very, very basic start of the API key per bucket: https://github.com/hxrsmurf/backblaze-php

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants