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

Fails to authorize when trying to access Dropbox via Cyberduck #6670

Closed
cyberduck opened this issue May 5, 2012 · 2 comments
Closed

Fails to authorize when trying to access Dropbox via Cyberduck #6670

cyberduck opened this issue May 5, 2012 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented May 5, 2012

6916e7d created the issue

I am on Windows XP SP3. I downloaded the connection profile and try to access my Dropbox via Cyberduck. After entering my Dropbox credentials it returns "Unauthorized". The same happens when I type in my App key/secret first. I tried all the combinations of Dropbox credentials and key/secret, but it returns "Unauthorized", "Forbidden" and "Provide additional login credentials", again and again. I would like to ask if getting the pair of App key/secret is all that's required to get accress to my Dropbox through Cyberduck, or do I need to go through all the programming stuff listed on the Dropbox developers page, like installing the python SDK, writing my own App(absolutely no idea) and the like? Thanks!!!!

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 9, 2012

@dkocher commented

Getting the application credentials should suffice.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 9, 2012

@dkocher commented

Duplicate for #6427.

Loading

@cyberduck cyberduck closed this May 9, 2012
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants