[GH-ISSUE #2182] [feature]: Socket.io key-values in the auth object #741

New issue

Open

opened 2026-03-16 16:58:39 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 16:58:39 +03:00

Owner

Originally created by @SeanCassiere on GitHub (Mar 21, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2182

Is there an existing issue for this?

I have searched the existing issues

Summary

Currently, the socket.io connection in the app only allows for Bearer token authentication into a socket server. However, Socket.io officially supports authentication into a server using the auth object with the server using middleware to handle verification.

Why should this be worked on?

As per the Socket.io client-options docs, a supported method of authentication/connection into the server is by sending key-value pairs within the auth object of the connection request. As this is an officially documented method of usage, this should be supported within the app.

Originally created by @SeanCassiere on GitHub (Mar 21, 2022). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2182 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary Currently, the socket.io connection in the app only allows for Bearer token authentication into a socket server. However, Socket.io officially supports authentication into a server using the `auth` object with the server using middleware to handle verification. ### Why should this be worked on? As per the [Socket.io client-options docs](https://socket.io/docs/v4/client-options/#auth), a supported method of authentication/connection into the server is by sending key-value pairs within the auth object of the connection request. As this is an officially documented method of usage, this should be supported within the app.