Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OAuth 2.0 - how to handle different token field in response #10838

Open
1 task done
ash007-postman opened this issue Apr 12, 2022 · 1 comment
Open
1 task done

OAuth 2.0 - how to handle different token field in response #10838

ash007-postman opened this issue Apr 12, 2022 · 1 comment

Comments

@ash007-postman
Copy link

Is there an existing request for this feature?

  • I have searched the existing issues for this feature request

Is your feature request related to a problem?

On behalf of the user:

We are evaluating Postman for a team, where we need to authenticate against an OAuth 2.0 endpoint. The integration authentication works great, but the token is returned in a body field called AccessToken instead of access_token. Therefore the Postman UI does not allow to "use" the Token. We have to copy it to the clipboard and paste in in the Token field instead. This isn't very user-friendly and is against my proposal of considering Postman for some common daily business.

Describe the solution you'd like

Configuration or workaround to allow the UI to work.

image

Describe alternatives you've considered

No response

Additional context

No response

@geniqtech
Copy link

Any updates regarding this feature? The OAuth 2.0 server I'm interfacing returns the token in field "token". Would be nice if we can customize which field to use for retrieving the token data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants