[
https://issues.apache.org/jira/browse/LIBCLOUD-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185611#comment-14185611
]
ASF GitHub Bot commented on LIBCLOUD-625:
-----------------------------------------
GitHub user erjohnso opened a pull request:
https://github.com/apache/libcloud/pull/379
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.
[1]
https://github.com/apache/libcloud/commit/20d977075117f05a0d8cd8ceb91c4dfcd93a7766
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/erjohnso/libcloud GCE_auth_fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/379.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 #379
----
commit f4c1396b4632acafba8f7bc6ab7d083dfbfe11e9
Author: Eric Johnson <[email protected]>
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: 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)
