Websocket service user authentication about websocket-node HOT 3 CLOSED

You don't necessarily need to do it at the HTTP header level. You could always do it yourself in your protocol.

from websocket-node.

Yes. Theoretically you could use HTTP basic auth, but I wouldn't recommend it. The WebSocket specification does not include any kind of authentication mechanism. It is left to the individual protocol designer to decide how best to perform authentication in their application.

The simplest thing to do might be to send the credentials from the client as the first message after the connection is successful, and then send back a response from the server, additionally closing the connection if the authentication failed. Obviously the server shouldn't process any other kind of messages until the authentication phase is complete.

Sent from my iPhone

On Jan 6, 2013, at 2:17 PM, Andrew Faulds [email protected] wrote:

You don't necessarily need to do it at the HTTP header level. You could always do it yourself in your protocol.

—
Reply to this email directly or view it on GitHub.

from websocket-node.

That's precisely what I do. The easiest way is just to do conn.once('message', function () { ... }), and then set your normal message handler (conn.on('message', function () { ... })) in that handler if the login was correct.

from websocket-node.