You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Chris Custine (JIRA)" <ji...@apache.org> on 2014/07/22 11:30:40 UTC
[jira] [Created] (JCLOUDS-633) Support passing bearer token
directly for OAuth2
Chris Custine created JCLOUDS-633:
-------------------------------------
Summary: 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
Priority: Minor
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)