Server-side authorize function does not work as advertised in README example about socketio-jwt HOT 4 CLOSED

I was able to fix it for my use case. The above code snippet removes the TS errors, and the problem with my key was algorithm RS256 instead of the default. Now, it seems to work.

However there was basically no feedback from the library on what was going on, and whether there was or wasn't a connection. It would be nice to have an option to see why the authorization failed.

from socketio-jwt.

Thanks for your report! @yoruvo
So as I understood you find out how to fix your problem but you would like to have more/better error message so you could fix it more easily. Also that, decodedToken should have a better type.

Sounds good to me, we're open to PR, if you have some time to open a PR to improve that, we would really appreciate it! 👌

from socketio-jwt.

Hi @divlo,

part of my issue came from my own mistake of using the wrong algorithm, sure. Still, the fact remains that your TS server example in the README doesn't work at all, due to the reasons outlined in the ticket.

Above I wrote some example code that does work, but it's quite ugly because your typing for decodedToken is either null, string, or a Record<string,any>. Is that supposed to be the case? Is it possible for decodedToken to be all these things in a JWT token context? I'm not familiar with the architecture, but it seems too lightly typed.

from socketio-jwt.

Indeed, the typings were wrong for decodedToken, I released @thream/[email protected] so now the example in the README work as expected, feel free to open others issues if any.
Thanks again for your contribution and hopefully it fix your problem. 🎉 @yoruvo

from socketio-jwt.