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

Google Storage API version 2 support #5955

Closed
cyberduck opened this issue May 13, 2011 · 10 comments
Closed

Google Storage API version 2 support #5955

cyberduck opened this issue May 13, 2011 · 10 comments
Assignees
Labels
enhancement fixed googlestorage version:4.0.2
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented May 13, 2011

107c120 created the issue

Will Cyberduck support the new Google Storage API version 2 with the new OAuth 2.0 authentication scheme?

Google only allows you to associate one Project for legacy access (which cyberduck uses) and it prohibits other projects from having this ability. I would love to take advantage of the new features and enhancements that Google Storage has introduced.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 13, 2011

@dkocher commented

Related to this I have also observed issues with creating buckets in EU and a subsequent incomplete bucket listing.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 13, 2011

@dkocher commented

OAuth is not really feasible for desktop applications to my knowledge.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 13, 2011

@dkocher commented

Replying to [comment:2 dkocher]:

OAuth is not really feasible for desktop applications to my knowledge.

  • Where to store the client secret?
  • Login requires HTTP form post.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 13, 2011

@dkocher commented

Replying to [comment:3 dkocher]:

Replying to [comment:2 dkocher]:

OAuth is not really feasible for desktop applications to my knowledge.

  • Where to store the client secret?
  • Login requires HTTP form post.

Please correct me if I am wrong on these.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 18, 2011

@dkocher commented

Documentation in OAuth 2.0 for native applications.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 18, 2011

@dkocher commented

Corresponding ticket for jets3t.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 4, 2011

@dkocher commented

Replying to [comment:6 dkocher]:

Corresponding ticket for jets3t.

Changes pulled into Jets3t in (https://bitbucket.org/jmurty/jets3t/pull-request/1/logging-configuration-support-for-google).

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 4, 2011

@dkocher commented

There is still the issue that for OAuth we have to store an application ID and secret which cannot be kept secure for a desktop application.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 8, 2011

@dkocher commented

In 0f680d6. To use OAuth2 with API version 2, use your x-goog-project-id for the username.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 8, 2011

@dkocher commented

Updated documentation.

@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
enhancement fixed googlestorage version:4.0.2
Projects
None yet
Development

No branches or pull requests

2 participants