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
Hi!
I'm trying to implement JIRA authentication through bell. JIRA uses RSA-SHA1 to create signatures. Unfortunately, it looks like bell uses HMAC-SHA1 every single time, without letting us change the algorithm; is that correct?
So based on that, I think we could definitely add support. Feel free to contribute a PR. BTW, we do not use node-oauth.
This should be a provider option that that defaults to HMAC-SHA1 and also allows RSA-SHA1 only. By searching the HMAC-SHA1 in /lib/oauth.js it should be very straightforward.
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
lockbot
locked as resolved and limited conversation to collaborators
Jan 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi!
I'm trying to implement JIRA authentication through bell. JIRA uses RSA-SHA1 to create signatures. Unfortunately, it looks like bell uses HMAC-SHA1 every single time, without letting us change the algorithm; is that correct?
RSA-SHA1 is supported by
node-oauth
, whichbell
seems to use.Is there any way to change the signing algorithm? Thanks!
The text was updated successfully, but these errors were encountered: