Open davidalpert opened 3 years ago
Hi @davidalpert , thank you for your suggestion. I'm fine with a feature flag, this might be useful for some. Could you add a test for this change?
thank you @SimonMiaou; it's been a while since I looked at this change but thank you for the feedback.
let me see if I can rebase this on top of latest (to resolve conflicts) and add a test for the change.
this PR should help address #232
previously an empty
oauth_token
parameter was appended to the query before sending it to jira when the:auth_type
parameter was set to:oauth_2legged
, but it appears that oauth v0.5.5 is appending the actual value ofoauth_token
as a parameteras a result the code which was appending an empty
oauth_token
parameter was actually appending it to the existingoauth_token
value, thereby corrupting the token and resulting in a vagueerror. I had to look at the detail in the server
atlassian-jira.log
file in order to see the actual problem.in order to preserve behaviour and backwards compatibilty with the previous release of the jira-ruby gem, this commit introduces a new feature flag
:append_explicit_oauth_token_parameter
which defaults to true, same as before, but can now be explicitly toggled off to avoid corrupting the access token in this way.using this commit I am able to query for jira issues via JQL without my username and password but instead using client options configured like this:
I welcome feedback on: