jwt.verify issue with asymmetric algorithms (RS256, ES256, PS256) #122
Description
What version of Elysia is running?
No response
What platform is your computer?
No response
What steps can reproduce the bug?
Hi,
I'm opening the issue as I spotted its resolution within #119 which is kind of labelled as refactoring.
jose jwtVerify except a public key for signing asymmetric algorithms (RS256, ES256, PS256). Given the plugin currently passes the all key to the function, it's currently impossible to use jwt.verify() with such algorithm. The result is always false regardless of how the private key is set and if valid.
What is the expected behavior?
No response
What do you see instead?
No response
Additional information
No response
Have you try removing the node_modules and bun.lockb and try again yet?
No response