oauth2: ignore monotonic time when considering whether Tokens are expired

This change ensures time comparisons Token expiry checking uses the wall
clock instead of the monotonic clock.

This situation can occur on laptops which enter sleep mode and don't
advance their monotonic clock.

Change-Id: If8518e96ca04f2137db4703440ff3b851d221aae
Reviewed-on: https://go-review.googlesource.com/83575
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
1 file changed
tree: c35807c72cb6c6a2503f352081705387dc68d3d5
  1. amazon/
  2. azure/
  3. bitbucket/
  4. clientcredentials/
  5. facebook/
  6. fitbit/
  7. foursquare/
  8. github/
  9. google/
  10. heroku/
  11. hipchat/
  12. internal/
  13. jws/
  14. jwt/
  15. linkedin/
  16. mediamath/
  17. microsoft/
  18. odnoklassniki/
  19. paypal/
  20. slack/
  21. twitch/
  22. uber/
  23. vk/
  24. yandex/
  25. .travis.yml
  27. client_appengine.go
  30. example_test.go
  32. oauth2.go
  33. oauth2_test.go
  34. README.md
  35. token.go
  36. token_test.go
  37. transport.go
  38. transport_test.go

OAuth2 for Go

Build Status GoDoc

oauth2 package contains a client implementation for OAuth 2.0 spec.


go get golang.org/x/oauth2

Or you can manually git clone the repository to $(go env GOPATH)/src/golang.org/x/oauth2.

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 golang.org/x/net/context package

This means it‘s 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 "google.golang.org/appengine" 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 "google.golang.org/appengine"
	newurlfetch "google.golang.org/appengine/urlfetch"


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},

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://golang.org/doc/contribute.html.

The main issue tracker for the oauth2 repository is located at https://github.com/golang/oauth2/issues.