API for other services about auth-socket HOT 7 OPEN

One benefit of the low level api is that I could create a websocket server that accepts all streams. MuxDemux it and then try authenticate just sub streams.

This means we can have both public and authenticated websocket apis in one server.

We may also want to consider simplifying the authHandler like (req, cb) {}.

There is also an alternative type of authentication you can do which would look like (stream, cb) {} where stream is a websocket connection. i.e. authentication could be a handshake over the websocket connection. This would require handling the upgrade for all websockets and then doing auth.

from auth-socket.

worked on this a little, try cloning and doing npm install and npm start in one tab, and npm run watch in another

then open:

http://localhost:8080/socket.html (user should be null)

and

http://localhost:8080/socket.html?hello=hello (user should be 'bob')

from auth-socket.

also I couldn't get wss.on("connection" to fire when using wss.handleUpgrade, maybe its a bug in ws??

from auth-socket.

ahh they emit it here https://github.com/einaros/ws/blob/master/lib/WebSocketServer.js#L72-L75

but if you use handleUpgrade manually it won't emit a connection event :(

from auth-socket.

ok just published v1.0.0, check it out :D

from auth-socket.

@maxogden I had to emit a connection event myself ( https://gist.github.com/Raynos/7651349#file-auth-socket-js-L29 )

from auth-socket.

@maxogden nice. the client one looks good. the doorknob / persona one doesn't use auth yet.

from auth-socket.