Google Storage API version 2 support

[cyberduck]

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]

@dkocher commented

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

[cyberduck]

@dkocher commented

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

[cyberduck]

@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]

@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]

@dkocher commented

Documentation in OAuth 2.0 for native applications.

[cyberduck]

@dkocher commented

Corresponding ticket for jets3t.

[cyberduck]

@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]

@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]

@dkocher commented

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

[cyberduck]

@dkocher commented

Updated documentation.