-
Notifications
You must be signed in to change notification settings - Fork 991
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
Add scope to token refresh request #448
base: master
Are you sure you want to change the base?
Conversation
This PR (HEAD: ff6afb7) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/oauth2/+/264037 to see it. Tip: You can toggle comments from me using the |
Message from Go Bot: Patch Set 1: Congratulations on opening your first change. Thank you for your contribution! Next steps: Most changes in the Go project go through a few rounds of revision. This can be Please don’t reply on this GitHub thread. Visit golang.org/cl/264037. |
This PR (HEAD: cf02433) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/oauth2/+/264037 to see it. Tip: You can toggle comments from me using the |
This PR (HEAD: fa2a674) has been imported to Gerrit for code review. Please visit https://go-review.googlesource.com/c/oauth2/+/264037 to see it. Tip: You can toggle comments from me using the |
I would be interested in this. The VW api needs the scopes during token refresh. |
any updates about this ? It is actually quiet common to require scopes in the token refresh request |
Microsoft for example requires scopes in the refresh response: https://docs.microsoft.com/en-us/graph/auth-v2-user?context=graph%2Fapi%2F1.0&view=graph-rest-1.0#5-use-the-refresh-token-to-get-a-new-access-token |
Message from zakaria amine: Patch Set 3: (1 comment) Please don’t reply on this GitHub thread. Visit golang.org/cl/264037. |
actually, it seems like even if Microsoft mentions that scopes are required, the refresh request is successfull without |
In relation to the proposal https://groups.google.com/g/golang-nuts/c/RJSNRbUvIPE/m/1qW_D6uMBAAJ I would propose a slightly different approach. Instead of adding additional options to the existing token refresh handling, I would prefer if a custom token refresher could be specified that allows fully tweaking the refresh, e.g. by adding the required headers needed for #483. Didn't receive any feedback on groups though. |
Thanks (Not sure about the |
Not sure there's much use in another PR. I've commented in the groups discussion, maybe it can spark some interest. |
Fixes #447