Postman 7.35 just made its first appearance on our downloads page. You’re probably wondering what’s new in it so let me break it to you, it’s all about OAuth 2! It also turns out that my esteemed colleague @premang.vikani1 had already written about it so I’ll be stealing his words for this post.
You can now save the information required to generate an OAuth token with the request or collection and you won’t have to enter these details again when you’re generating a new token. This information will be sharable with the request/collection as well.
This is helpful if you have multiple requests using different OAuth servers or if you’re sharing a request with someone and they need the details to generate the token.
A word of caution: OAuth token generation information can contain sensitive data. Like other authentication methods, we encourage you to use environment variables to mask this when sharing the request or collection.
Share OAuth 2.0 parameters
An OAuth token contains sensitive information and hence, it should be shared carefully. You can now optionally choose to share a token with the request or collection. All you have to do is sync the token. By default, we will not sync it. If you don’t sync the token, it will still be present in your local session and can be used by you in the app but it won’t be stored with the request on Postman cloud.
As usual we’ve also pushed various improvements and bug fixes. For example, if you’re working with a lot of environment variables, the experience should now be much smoother. You can find the complete list of improvements and bug fixes in the complete release notes.
These updates look great, but unfortunately, for all of my collections after upgrading to 7.35 - all of my Oauth2 details have been wiped… The form is completely blank as if I’m starting from scratch? Everything else seems to be there for my collection - is this happening to anyone else?
Some additional info - I’m running the Postman native app on macOS Catalina, Version 10.15.7
You’ll also notice the form does not look the same as what you’ve described in this post… I have “Configure New Token” vs. the “Generate New Access Token” dialogue you’ve shown in your screenshot.
You can also retrieve your ‘lost’ auth settings at any time by opening developer window (⌘⌥I or ctrl + shift + I) and writing the following command in the console: pm.models.authhelperstate.find('oAuth2-meta').then((data) => console.log(data))
I’m seeing that as well - all previous token credentials wiped. Worse:
Even reentering all the credentials does not always work. Sometimes, the app gets stuck on an old token and won’t update the request no matter what I do, even though I am able to get a new token, see it in the token library, and click “use token”.
I can’t roll back to 7.34. The installer detects the newer install and errors out.
Since 7.35 has now been pulled for 5 days, this seems like a bad bug and the release should never have made it out of beta.
I’ve run into the same issue. I had problems using OAuthV2.0 and getting authenticated, so I tried uninstalling and reinstalling 7.34, but now I cannot install Postman due to the installer. This impacts my ability to work… so I’m hoping they rectify this issue soon.
Thanks for the help! Does this imply that a fixed 7.35 is still a ways off? It’s been a week since the initial release was pulled. Since you’re still advising users to go through a messy manual de-installation process, that does not seem to bode well for 7.35…
Postman on my machine updated to 7.35 few days back and today I tried to rollback to older version due to some bugs (trying to select new token and use it, when Auth mode = OAUTH 2 with client creds). When I tried to install older version, it threw “Version mismatch detected”. I thus killed my older version, had to removed both Postman versions from Applications folder (am using Mac) and when I went out to download 7.35 which I had first, I couldn’t find it anywhere.
I had been to https://www.postman.com/downloads/ and it downloads 7.34, which again gives same “Version mismatch detected” error, halting everything.
Thank you, will do that. I deleted all versions after backing up my collections and downloaded Canary. I couldn’t find a solution other than that, at that time.
You’re probably wondering what’s new in it so let me break it to you, it’s all about OAuth 2! It also turns out that my esteemed colleague @premang.vikani1 had already written about it so I’ll be stealing his words for this post. 
