libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-568) Fixing cross service OAuth scopes for Google Compute Engine / DNS / Storage
Date Mon, 09 Jun 2014 18:35:01 GMT

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

ASF GitHub Bot commented on LIBCLOUD-568:
-----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/libcloud/pull/302


> Fixing cross service OAuth scopes for Google Compute Engine / DNS / Storage
> ---------------------------------------------------------------------------
>
>                 Key: LIBCLOUD-568
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-568
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Compute, DNS, Storage
>            Reporter: Eric Johnson
>
> Currently, a user cannot authenticate to both Google Compute Engine and Google Cloud
DNS at the same time.  Each underlying call to "get_driver()" sets a specific OAuth scope
that precludes authorization to the other service.
> Incoming fix propagates scopes set during create_driver() down to the connection class.
 If no scopes are set (likely the main use-case), then full read/write scopes are set for
Compute, Storage, and DNS.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message