I am using Postman to invoke a GraphQL subscription over the WebSocket protocol and observed that the Authorization token must be explicitly added in the request headers.
Additionally, when the proxy fails to authorize the token, Postman appears to enter an infinite retry loop, continuously re-triggering the request. I tested the same flow using Insomnia, where it works as expected (noting that Insomnia has its own limitations).
I recall that authorization was working correctly with an earlier version of Postman. I am able to consistently reproduce this issue.
Has anyone else observed similar behavior, or is there a known fix or recommended workaround?
Appreciate your quick support.
Hi @research-architect-7 Thanks for reaching out.
I am able to send an authorization header in the connection params for a GraphQL subscription request over WebSocket.
Could you please try the following?
- Update your Postman app to the latest version? We had an issue with the auth header and had promptly fixed it.
If the above doesn’t work, please provide the following information so we can help with this:
- Which version of Postman you’re using? (You can get this by going to Settings → About)
- Are you using Web + Desktop agent?
- Which auth method are you using (Basic/API Key etc)?
Do keep us posted.
Thank you!
Hi,
I upgraded Postman to the latest version (11.76.4) last night and am still observing the same issue.
Please note that I am not using the WebSocket connector in Postman. Instead, I am using the GraphQL (Beta) connector to invoke a GraphQL subscription over WebSocket.
I have attached a screenshot highlighting the observed behavior.
Regardless of whether OAuth 2.0 authorization is configured with an active token or an expired token, I am seeing the same behavior. Additionally, prior to the upgrade, I was able to explicitly set the Authorization header using Bearer <token>. After upgrading, this approach is no longer working.
Please note that Postman does not appear to recognize or honor the WebSocket close signal and continues to repeatedly retry the connection. As a result, I have to explicitly terminate Postman to stop the behavior. This is becoming disruptive and is also generating unnecessary and heavy traffic to the proxy within our network.
Is there a way we can connect so I can demonstrate the issue live? Unfortunately, I am unable to upload a screen recording due to new-user limitations.
Postman Version Details:
Appreciate your assistance.
Let me know if additional information is required. This is critical and needs your urgent support.
Thanks a lot for providing the information @research-architect-7 This was helpful. We’re looking into this and will come back with an update as soon as possible.
Any further update? Appreciate if you can consider looking into this on priority
follow-up.. if there are any further update on this thread. @devesh-kumar-postman
Hi Ankit, we’ve already identified the issue and will promptly fix this.
Thank you very much for pointing this out and your patience, we truly appreciate it. Apologies for the time taken.
thank you @devesh-kumar-postman , any eta so that we can align our activity around those dates.
Hi Ankit, we’ve lined up the fix for release and it should be delivered to you by early Friday. I’ll post here when the fix is released and available to users.
Thank you so much for reporting this, your patience and understanding.
Hi Ankit, this issue should now be fixed, you can choose any auth method available in a GraphQL subscription request, set the credentials to be added to request headers and they should reflect correctly in your request.
Please update Postman to the latest version (v11.80.3) for the fix.
We thank you for your patience and for reporting this bug.
2 Likes
