[
https://issues.apache.org/jira/browse/LIBCLOUD-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179662#comment-14179662
]
ASF subversion and git services commented on LIBCLOUD-625:
----------------------------------------------------------
Commit 91a9be4282485d484a7d1f3b9749db86f442c4f4 in libcloud's branch
refs/heads/trunk from [~kami]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=91a9be4 ]
Merge branch 'trunk' into LIBCLOUD-625_gce_auth_internal
Closes #376
> 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)
