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 tracker for existing similar issues and I know that duplicates will be closed
Describe the Issue
When selecting "Get New Access Token" and choosing "Authorize using browser", Postman does not successfully retrieve the token. The browser-based authentication completes successfully, but Postman remains stuck on the "Get new access token" dialog and never receives the token. Pop-ups are allowed in the browser, so that is not the issue.
While investigating, I noticed that Postman’s JavaScript calls window.open(url) with a callback URL that looks like this:
postman://app/oauth2/callback#access_token=[access token]&token_type=Bearer&expires_in=5107&scope=https%3a%2f%2fvault.azure.net%2fuser_impersonation+https%3a%2f%2fvault.azure.net%2f.default&session_state=[session state GUID]
If I take this URL and paste it into the browser as-is, nothing happens. However, if I remove the session_state query parameter and paste the remaining URL into the browser, Postman immediately receives the token. This suggests that the handling of the session_state parameter might be causing the issue.
Is there an existing issue for this?
Describe the Issue
When selecting "Get New Access Token" and choosing "Authorize using browser", Postman does not successfully retrieve the token. The browser-based authentication completes successfully, but Postman remains stuck on the "Get new access token" dialog and never receives the token. Pop-ups are allowed in the browser, so that is not the issue.
While investigating, I noticed that Postman’s JavaScript calls window.open(url) with a callback URL that looks like this:
postman://app/oauth2/callback#access_token=[access token]&token_type=Bearer&expires_in=5107&scope=https%3a%2f%2fvault.azure.net%2fuser_impersonation+https%3a%2f%2fvault.azure.net%2f.default&session_state=[session state GUID]
If I take this URL and paste it into the browser as-is, nothing happens. However, if I remove the session_state query parameter and paste the remaining URL into the browser, Postman immediately receives the token. This suggests that the handling of the session_state parameter might be causing the issue.
Environment Details:
Postman version: 11.22.1
Steps To Reproduce
Screenshots or Videos
Operating System
Windows
Postman Version
11.22.1
Postman Platform
Postman App
User Account Type
Signed In User
Additional Context?
No response
The text was updated successfully, but these errors were encountered: