libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From erjohnso <...@git.apache.org>
Subject [GitHub] libcloud pull request: [LIBCLOUD-568] Fixing cross service OAuth s...
Date Fri, 30 May 2014 12:42:32 GMT
GitHub user erjohnso opened a pull request:

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

    [LIBCLOUD-568] Fixing cross service OAuth scopes for Google Compute Engine / DNS / Storage

    Prior to this fix, a user could call "get_driver()" for GCE but authorization was only
allowed for the "compute" scope.  With the addition of the DNS module, users calling its "get_driver()"
would only be authorized to the DNS service.
    
    This change allows scopes to be set as keyword params in get_driver() (or via secrets.py)
that get propagated down to the authorization connection class.  The default behavior is to
grant authorization via scopes to all supported google services (compute, storage, dns).
    
    It should be noted that the storage authorization via oauth scopes is bogus, but sets
the stage for future enhancements we expect to contribute over the summer.
    
    @wrigri, @franckcuny - A review would be much appreciated!

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/erjohnso/libcloud LIBCLOUD-568_google_oauth

Alternatively you can review and apply these changes as the patch at:

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #302
    
----
commit 23e86256770e389741196d59f00554e8b76ea2d5
Author: Eric Johnson <erjohnso@google.com>
Date:   2014-05-30T12:33:47Z

    update to allow simultaneous authorization for all supported google services

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message