You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
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.
Is there an existing request for this feature?
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 ofaccess_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.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: