« Changelog History


SocketCluster v13.1.3 Release Notes

Release Date: 2018-05-13 // almost 6 years ago
    • 0️⃣ You can now pass an optional authVerifyAlgorithms array (of strings) to the main SocketCluster instance (used for JWT auth verification). If not specified, by default the algorithm will be the same for both JWT signing and verification (determined by authAlgorithm). The consequence of this change is that while you can only sign with one algorithm, the verification could accept multiple algorithms.
    • The SC server adds a socket property to the options object which is passed to the verifyToken method of the authEngine; this means that if a custom authEngine is provided, it can use data from the socket itself (e.g. cookie or query string) to aid in performing the verification.
    • ➕ Added a destroy method on the server side socket to make it more consistent with the client side socket. Also added a matching active (boolean) property which can be used to check if the socket was destroyed.
    • An error event will be emitted on the socket if the user tries to emit a reserved event on that socket.
    • 📇 Renamed SCSocket to SCServerSocket.
    • ⬆️ Bumped sc-uws version.