You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would you consider accepting an object for the algorithm parameter in jwsVerify, as well checking for the presence of opts.algo in jwsSign? This would involve checking for string vs object to decide whether to use jwa or use it as is.
This way someone could pass {sign: function, verify: function} to support custom algorithms without needing to rewrite this module.
The text was updated successfully, but these errors were encountered:
Let me refresh this topic since I have similar issue. Seems that there is a need for such feature - question is, on which level - node-jws or maybe node-jsonwebtoken (where I created PR for this already: auth0/node-jsonwebtoken#429)
Would you consider accepting an object for the algorithm parameter in jwsVerify, as well checking for the presence of opts.algo in jwsSign? This would involve checking for string vs object to decide whether to use jwa or use it as is.
This way someone could pass
{sign: function, verify: function}
to support custom algorithms without needing to rewrite this module.The text was updated successfully, but these errors were encountered: