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-625) GCE: When used on a GCE instance, auth should use metadata tokens
Date Tue, 28 Oct 2014 11:43:33 GMT

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

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

Github user erjohnso closed the pull request at:

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


> GCE: When used on a GCE instance, auth should use metadata tokens
> -----------------------------------------------------------------
>
>                 Key: LIBCLOUD-625
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-625
>             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.
> https://cloud.google.com/compute/docs/authentication



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message