Jim Cote

I have implemented a version of this idea at [github.com/jfcote87/oauth2](https://github.com/jfcote87/oauth2),

I wrote this fork to handle that problem, github.com/jfcote87/oauth2. It is in production. On Tue, Jun 21, 2022 at 9:45 AM jens1205 ***@***.***> wrote: > Having a golang oauth2 library...

You could also just cache the Token from created from the Config.Exchange() func so that you only cache Token once because the refresh token never expires.

Token.RefreshToken stays the same. Token.AccessToken changes. See if the following gist explains it any better. https://gist.github.com/jfcote87/89eca3032cd5f9705ba3

The RefreshToken does not change. so you don't have to worry about the background refresh. The tokenRefresher struct stores the RefreshToken in the oldToken field and this field is not...

I think I see where we might be talking past each other and that an actual bug exists. I tested code using Google's client apis and their implementation of oauth2....

https://tools.ietf.org/html/rfc6749#section-6 Section 6. Refreshing an Access Token (_last paragraph_, emphasis in original) The authorization server MAY issue a new refresh token, in which case the client MUST discard the old...

Bill, I have a CL ready that fixes the refresh token problem and will upload later today. @rakyll are you ok with calling this a bug? Should we start a...

This error still exists in the current swagger definition.