You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: