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’ve been evaluating Postman for my organisation and it looks really promising. However one area that may prevent our adoption is the current method of obtaining OAuth 2.0 tokens:
Our organisation is deeply uncomfortable with sharing of the Client Secret.
We are first-party consumers of our own internal APIs and don’t make use of an Authorization URL.
We can easily obtain the required OAuth 2.0 details (access token, refresh token, expiry, etc) and ideally we would like a way to import them (perhaps from JSON or manually entered) so the tokens are stored in the same way as the existing method.
The text was updated successfully, but these errors were encountered:
Also, one thing I'm not sure about is if the access token has expired, will Postman transparently use the refresh token to obtain a new access token and update it?
@stajs You can share an environment across your team, which can have the oauth token.
And then everyone can use that env var in the Oauth-2 input. Would that work for you?
I’ve been evaluating Postman for my organisation and it looks really promising. However one area that may prevent our adoption is the current method of obtaining OAuth 2.0 tokens:
Client Secret
.Authorization URL
.We can easily obtain the required OAuth 2.0 details (access token, refresh token, expiry, etc) and ideally we would like a way to import them (perhaps from JSON or manually entered) so the tokens are stored in the same way as the existing method.
The text was updated successfully, but these errors were encountered: