google: Re-enable AppEngineTokenSource to be used from Managed VMs.

Fixes #152.

Change-Id: I757c011d3ac5dca8f80fb2119eda3adf8c178ca6
Reviewed-by: Andrew Gerrand <>
3 files changed
tree: c975e8e16ebfc6696920863945f02b73004adb17
  1. clientcredentials/
  2. facebook/
  3. github/
  4. google/
  5. internal/
  6. jws/
  7. jwt/
  8. linkedin/
  9. odnoklassniki/
  10. paypal/
  11. vk/
  12. .travis.yml
  18. client_appengine.go
  19. example_test.go
  20. oauth2.go
  21. oauth2_test.go
  22. token.go
  23. token_test.go
  24. transport.go
  25. transport_test.go

OAuth2 for Go

Build Status

oauth2 package contains a client implementation for OAuth 2.0 spec.


go get

See godoc for further documentation and examples.

App Engine

In change 96e89be (March 2015) we removed the oauth2.Context2 type in favor of the context.Context type from the package

This means its no longer possible to use the “Classic App Engine” appengine.Context type with the oauth2 package. (You're using Classic App Engine if you import the package "appengine".)

To work around this, you may use the new "" package. This package has almost the same API as the "appengine" package, but it can be fetched with go get and used on “Managed VMs” and well as Classic App Engine.

See the new appengine package's readme for information on updating your app.

If you don't want to update your entire app to use the new App Engine packages, you may use both sets of packages in parallel, using only the new packages with the oauth2 package.

import (
	newappengine ""
	newurlfetch ""


func handler(w http.ResponseWriter, r *http.Request) {
	var c appengine.Context = appengine.NewContext(r)
	c.Infof("Logging a message with the old package")

	var ctx context.Context = newappengine.NewContext(r)
	client := &http.Client{
		Transport: &oauth2.Transport{
			Source: google.AppEngineTokenSource(ctx, "scope"),
			Base:   &newurlfetch.Transport{Context: ctx},