-
Notifications
You must be signed in to change notification settings - Fork 1k
Add additional headers during token refresh #483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Here is an example token source that supports custom refreshers:
One could easily take this forward and make the guard time configurable, too (#481). |
This would be useful to propagate tracing headers too. Besides, for new oauth2 requests, afaik the headers are hardcoded in an internal class: https://github.com/golang/oauth2/blob/master/internal/token.go#L173 (from current master c85d3e9) |
the package generally follows oauth2, not almost oauth2. |
Unfortunately, reality doesn't. I'm working with some ~30 apis that all made their little tweaks. Instead of reimplementing each and every code/token exchange request it would be great to use the oauth2.Config and supply the additional parameters. |
The VW api I'm working with (which is almost OAuth but then isn't) needs to receive the clientID in
X-Client-ID
header during token refresh. Would it be possible to add such header?The text was updated successfully, but these errors were encountered: