libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (LIBCLOUD-625) GCE: When used on a GCE instance, auth should use metadata tokens
Date Mon, 27 Oct 2014 18:57:35 GMT


ASF GitHub Bot commented on LIBCLOUD-625:

GitHub user erjohnso opened a pull request:

    GCE: fix GCE internal auth

    @Kami - Very sorry, but I think with the merge trouble we were having on LIBCLOUD-625[1],
I must have goofed on one of conflicts.  This minor change fixes LIBCLOUD-625.

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

    $ git pull GCE_auth_fix

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

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

    This closes #379
commit f4c1396b4632acafba8f7bc6ab7d083dfbfe11e9
Author: Eric Johnson <>
Date:   2014-10-27T18:53:29Z

    GCE: fix GCE internal auth


> GCE: When used on a GCE instance, auth should use metadata tokens
> -----------------------------------------------------------------
>                 Key: LIBCLOUD-625
>                 URL:
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Compute
>         Environment: Google Compute Engine
>            Reporter: Eric Johnson
> Currently, the GCE driver only supports authorization from a perspective that code is
executed "outside" of the GCE environment. However, if code is executed on an instance running
"inside" GCE, it is possible to handle authorization with GCE's internal metadata service
for an access token.
> When an instance is created with appropriate service account scopes, this access token
can be used to provide authorization to access the corresponding Google Cloud services.

This message was sent by Atlassian JIRA

View raw message