Skip to content
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

why passing requests kwargs that may contain request params to refresh_token request ? #491

Open
ollofx opened this issue May 13, 2022 · 1 comment

Comments

@ollofx
Copy link

ollofx commented May 13, 2022

9188065

this is an issue, as it sends to the request_token url anything passed to a regular request and add it to the body of refresh_token

is there any justification ? what is sent to the regular end-point should not reach the refresh_token endpoint, only auto_refresh_kwargs should be used.

and why not using the client_id provided within the client, for instance for Legacy Application Flow

@jmoraleda
Copy link

I believe this the same as issue 3 in #264

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants