[
https://issues.apache.org/jira/browse/JCLOUDS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Custine resolved JCLOUDS-633.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
1.8.1
Assignee: Chris Custine
> Support passing bearer token directly for OAuth2
> ------------------------------------------------
>
> Key: JCLOUDS-633
> URL: https://issues.apache.org/jira/browse/JCLOUDS-633
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-labs-google
> Affects Versions: 1.7.3
> Reporter: Chris Custine
> Assignee: Chris Custine
> Priority: Minor
> Fix For: 1.8.1, 2.0.0
>
>
> Currently the oauth code requires a service account for credentials and
> jclouds manages fetching a token and caching it. This is not ideal when
> integrating jclouds into a UI for any kind of tooling which might already be
> authenticating with oauth and already has a token. In such cases it would be
> ideal to pass in the project ID or account email as well as the previously
> retrieved token and bypass the fetching and caching of a new token.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
