jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-633) Support passing bearer token directly for OAuth2
Date Wed, 13 Aug 2014 22:40:15 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096247#comment-14096247
] 

ASF subversion and git services commented on JCLOUDS-633:
---------------------------------------------------------

Commit bee9898559d1bf3c2a2701e94b05fe732ae6aa41 in jclouds-labs-google's branch refs/heads/1.8.x
from [~ccustine]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs-google.git;h=bee9898 ]

JCLOUDS-633: Support passing bearer token directly for OAuth2


> 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)

Mime
View raw message