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

Use of application keys for authentiation #10414

Closed
cyberduck opened this issue Aug 2, 2018 · 1 comment
Closed

Use of application keys for authentiation #10414

cyberduck opened this issue Aug 2, 2018 · 1 comment
Labels
b2 Backblaze B2 Protocol Implementation bug fixed high priority
Milestone

Comments

@cyberduck
Copy link
Collaborator

070a129 created the issue

My Backblaze B2 credentials aren't working (error: Access Denied. Unexpected Exception. Please contact your hosting provider for assistance). I've reported a similar error with another B2 integration partner and the response I received from BB:

"We recently put out a new authentication key system were you can create multiple extra keys for different purposes. Unfortunately not all of our integration partners have updated their clients to adapt to this change. If you are using one of these keys with ***** you may need to contact them to see when they can push out an update to their client.”

Is Cyberduck being updated to fix this?

Thank you

@cyberduck
Copy link
Collaborator Author

@dkocher commented

From my understanding authentication should just work. Please enter your application key id and not your Account ID in the username field which is only used when logging in with your master key. In 027170a.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
b2 Backblaze B2 Protocol Implementation bug fixed high priority
Projects
None yet
Development

No branches or pull requests

1 participant