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

b2client: Add the ability to use a restricted Application ID #475

Closed
wants to merge 1 commit into from

Conversation

bekriebel
Copy link

@bekriebel bekriebel commented Aug 2, 2018

B2 allows you to create Application IDs that are restricted to specific
buckets. To allow for this, read back the information provided by the
authorization request and use the allowed bucket permissions if they are
found.

An account-level Application ID will still continue to function
normally, as would an Application ID that has access to all buckets.

Fixes #484

B2 allows you to create Application IDs that are restricted to specific
buckets. To allow for this, read back the information provided by the
authorization request and use the allowed bucket permissions if they are
found.

An account-level Application ID will still continue to function
normally, as would an Application ID that has access to all buckets.
@CLAassistant
Copy link

CLAassistant commented Aug 2, 2018

CLA assistant check
All committers have signed the CLA.

@gilbertchen
Copy link
Owner

I just pushed commit 674d35e which is basically half of the changes in this PR. This other half (AllowedBucketID) isn't needed as Backblaze has fixed an issue in b2_list_buckets when an application key is used.

Thanks for your work!

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

Successfully merging this pull request may close these issues.

3 participants