I configured oauth 2.0 such that access token is refreshed properly, but when calling the “Refresh Roken URL“, a new refresh_token is passed aswell. How does postman properly deal with refresh_token rotation?
Hey @ugofoscolo ![]()
Welcome to the Postman Community! ![]()
You can find more details around the refreshing of the tokens using that feature, on our Postman Docs site.
Is that the information that you’re seeking?
When I click Refresh or postman feels like auto refreshing it, only the access token is refreshed/rotated.
In my response I also send back with the new access_token a new refresh_token but that new refresh token doesn’t get the place of the old one. I need that.
Could you please share some visual examples of what you’re seeing and what you’d expect to see?
This will really help the team understand your experience better ![]()