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 and I know that duplicates will be closed
Is your feature request related to a problem?
Can't use the WebSocket feature because my WebSocket endpoint requires authentication with AWS Signature.
Describe the solution you'd like
Ideally, the "Authorization" tab that is available when defining HTTP requests will simply be made available when defining WebSocket connections as well, and the auth settings simply applied to the initial HTTP handshake request.
Describe alternatives you've considered
No response
Additional context
Postman has great support for signing HTTP requests with AWS Signature. However, this feature is not supported for WebSocket connections.
WebSocket APIs built with AWS may require authentication using AWS Signature. It works exactly as in a REST API request, and is used to sign the initial HTTP request sent by the client to initiate the handshake for creating a new WebSocket connection.
Using the command line tool wscat and custom scripts, I have tested this successfully with the signature in the request URL, and verified it works as desired, allowing only connections that are properly signed and authenticated.
The text was updated successfully, but these errors were encountered:
Is there an existing request for this feature?
Is your feature request related to a problem?
Can't use the WebSocket feature because my WebSocket endpoint requires authentication with AWS Signature.
Describe the solution you'd like
Ideally, the "Authorization" tab that is available when defining HTTP requests will simply be made available when defining WebSocket connections as well, and the auth settings simply applied to the initial HTTP handshake request.
Describe alternatives you've considered
No response
Additional context
Postman has great support for signing HTTP requests with AWS Signature. However, this feature is not supported for WebSocket connections.
WebSocket APIs built with AWS may require authentication using AWS Signature. It works exactly as in a REST API request, and is used to sign the initial HTTP request sent by the client to initiate the handshake for creating a new WebSocket connection.
Using the command line tool
wscat
and custom scripts, I have tested this successfully with the signature in the request URL, and verified it works as desired, allowing only connections that are properly signed and authenticated.The text was updated successfully, but these errors were encountered: