OAuth 2.0 Refresh Token always sends basic auth

[DominicSaladin]

Is there an existing issue for this?

• I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

When using the auto token refresh feature or the manual refresh token feature, postman always sends a request with basic auth, even if the client authentication is set to "Send client credentials in body".

Also the use of the advances parameters doesn't seem to work for this:

The issue was reported one year ago for macOS #11668 and #12110

Steps To Reproduce

1. Set up Authorization for OAuth 2.0
2. Set client authentication to "Send client credentials in body"
3. Request a new access token
4. Refresh token
   

Screenshots or Videos

No response

Operating System

Windows

Postman Version

10.24.16

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

No response

[abhijeetborole]

Hey @DominicSaladin, thanks for reporting this issue. Postman takes a snapshot of the headers/body/url when the token is generated as this token is stored locally and available across collections and workspaces. Changes to the refresh request parameters will reflect when you generate a new token. Could you try to:

• Add the params you wish to override in the Refresh Request section, your current setup is fine to override the client_id and client_secret and send them in the body.
• Generate a new token once this configuration is setup in the Refresh Request section.
• Try refreshing this token.

Let me know if this fixes the issue for you.
E.g.

Screen.Recording.2024-04-05.at.12.04.34.PM.mov

[DominicSaladin]

Thanks @abhijeetborole that actually worked! But isn't that a weird behavior? When using Postman, this behavior is not clear and even if it takes a snapshot of the get access token request, why do I have to specify the client_id and client_secret manually?
When getting the access token, I don't have to specify those parameters and it gets sent like it should.