Last active
September 19, 2023 23:38
-
-
Save jfromaniello/8418116 to your computer and use it in GitHub Desktop.
Example of authenticating websockets with JWTs.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
var WebSocketServer = require('ws').Server; | |
var wss = new WebSocketServer({port: 8080}); | |
var jwt = require('jsonwebtoken'); | |
/** | |
The way I like to work with 'ws' is to convert everything to an event if possible. | |
**/ | |
function toEvent (message) { | |
try { | |
var event = JSON.parse(message); | |
this.emit(event.type, event.payload); | |
} catch(err) { | |
console.log('not an event' , err); | |
} | |
} | |
wss.on('connection', function(ws) { | |
ws.on('message', toEvent) | |
.on('authenticate', function (data) { | |
jwt.verify(data.token, options, function (err, decoded) { | |
//now is authenticated | |
}); | |
}); | |
ws.send('something'); | |
}); | |
@OBorce u get my point, that's why what I do is only save the userId as key to users object then save the token as it's value. so that every time the user's token changes u'll know which token to update due to the saved userId.
Is there any option to connect to a WebSocket through username and password authentication?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@ShejaEddy probably something like the token can expire and the client can keep the connection open forever?