JIRA WebHook firing, but resulting in 401

Clayton Taylor October 25, 2017

I am currently trying to use a JIRA WebHook to POST issue updates to an endpoint. (JIRA Server v7.2.7) The Jira log says:

httpclient-callbacks:thread-13 WARN anonymous     [c.a.webhooks.plugin.PublishTaskFactoryImpl$PublishTaskImpl] Client error - 401 when posting to web hook at 'https://{mydomain}.com:443/{path}'

The strange thing is, the error isn't coming from the server because there's no log entry for the 401. Also, if I spin up a simple localhost and change the URL in JIRA, then it works. Any idea why the WebHook's failing to post using https? Or if that's even the issue?

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 26, 2017

Hi Clayton,

There is a bug that might be related to this issue over at JRASERVER-42579

I can't say for sure that this applies in your case yet, because I think you have obscured the parts of the URL that might contain this information, but I am interested to see if perhaps you can share more of the URL you are using for this webhook.   I am not particularly interested in the domain or subdomain of the URL, but the rest of the syntax could be a factor here.

While that bug is directly concerning the conversion of a space character into the string of '%20', my concern is to see if any other parts of your URL contain any '%' characters as a means to substitute characters.   The site https://ascii.cl/ lists a Hex code conversion chart where certain characters can get converted into hex.   So your space can be converted into a %20 or a / can be converted into a %2F.   I am interested to learn more about the specific URL you are using, and then seeing if Jira might be converting the characters here into a hex code in order to be able to make this webhook call.   The concern here is that if this conversion is taking place that this might be causing a http error code of 401.

Regards,
Andy

Clayton Taylor October 27, 2017

That was exactly the issue. Thanks for the quick reply.

Suggest an answer

Log in or Sign up to answer