# Unable to generate new Oauth 2.0 access token

**URL:** <https://community.postman.com/t/unable-to-generate-new-oauth-2-0-access-token/2358>\
**Category:** Help Hub\
**Tags:** oauth2\
**Created:** [August 10, 2018, 6:04pm UTC](https://community.postman.com/t/unable-to-generate-new-oauth-2-0-access-token/2358 "2018-08-10T18:04:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gerstle](https://avatars.discourse-cdn.com/v4/letter/g/c68b51/32.png) [@gerstle](https://community.postman.com/u/gerstle)\
**Post date:** [August 10, 2018, 6:04pm UTC](https://community.postman.com/t/unable-to-generate-new-oauth-2-0-access-token/2358/1 "2018-08-10T18:04:35Z")

</div>

I’ve had an issue using OAuth 2.0 tokens for the last couple months. Sometimes it works fine for weeks on end, but sometimes I am completely unable to generate new tokens within postman.

Steps:

1. I’m using a 2015 MBP running High Sierra 10.13.6
2. Open postman
3. On a request, select `OAuth 2.0` as auth type, add data to `Request Headers`
4. Click `Get New Access Token`
5. Set fields…
  1. Token name: `sandbox`
  2. grant type: `Implicit`
  3. callback url: I’ve tried `https://www.getpostman.com/oauth2/callback` and a random localhost one
  4. auth url: my custom oauth2 implementation url
  5. client id: `postman`
  6. Client authentication: `Send as Basic Auth Header`

6. click `Request Token`
7. Login page loads, enter credentials, click `Login`
8. EXPECTED: login page to close and new token available in `manage access tokens` window
9. ACTUAL: login page simply refreshes. Re-attempting does the same thing

Restarting Postman does nothing. The only work around I have found is to wipe out my entire `~/Library/Application Support/Postman` directory and restart. This loses all local settings and I have to re-login. Not ideal.

Has anyone else experienced this and has a better work around? Am I doing something stupid?

cheers.  
casey.

---

<div class="post-metadata">

**Author:** ![mikeacc](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@mikeacc](https://community.postman.com/u/mikeacc)\
**Post date:** [August 20, 2018, 1:27pm UTC](https://community.postman.com/t/unable-to-generate-new-oauth-2-0-access-token/2358/2 "2018-08-20T13:27:50Z")

</div>

Sorry, I don’t have a solution, but I’ll give you a bump because I’ve been experiencing the same thing for months and it drives me nuts.

What I’ve ended up doing as a workaround is the actually use SOAPUI to get an access token and then copy and paste the access token into Postman. I love postman for my testing, but this issue has me considering just converting to SOAPUI.

---

<div class="post-metadata">

**Author:** ![gerstle](https://avatars.discourse-cdn.com/v4/letter/g/c68b51/32.png) [@gerstle](https://community.postman.com/u/gerstle)\
**Post date:** [August 20, 2018, 4:19pm UTC](https://community.postman.com/t/unable-to-generate-new-oauth-2-0-access-token/2358/3 "2018-08-20T16:19:49Z")

</div>

Yeah, I can do it via a web form as well, but it’s such a pain. It’s already painful enough within postman when it doesn’t automagically use the token you just generated by default 🙂

---

<div class="post-metadata">

**Author:** ![vdespa](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/vdespa/32/2770_2.png) [@vdespa](https://community.postman.com/u/vdespa)\
**Post date:** [August 9, 2019, 1:35pm UTC](https://community.postman.com/t/unable-to-generate-new-oauth-2-0-access-token/2358/5 "2019-08-09T13:35:34Z")

</div>

@tbehler Would be great to mention an example API which shows this problem and add a few screenshots.