Summary

When JIRA uses a Proxy Server to communicate with HTTP and/or HTTPS Servers, you can define the following Authentication arguments:
-Dhttp.proxyUser=atlaspirate -Dhttp.proxyPassword=yarrrrr -Dhttps.proxyUser=atlaspirate -Dhttps.proxyPassword=yarrrrr

These Arguments supply credentials to authenticate against a Proxy Server so that requests can be made.

This configuration is defined in: How to Configure an Outbound HTTP and HTTPS Proxy for JIRA

JIRA Webhooks do not appear to respect these configuration settings.

Environment

• JIRA using WebHooks

Steps to Reproduce

1. Set up a HTTP Web Proxy that Requires Authentication
2. Create a Simple WebHook that communicates over HTTP that needs to communicate with a Proxy Server due to: JRA-43143

Expected Results

1. JIRA should be able to authenticate consistently with Proxies. This would include WebHooks.
2. Webhooks should pass authentication of a Proxy server if the credentials of the proxy server are correct.

Actual Results

The following error has been seen in the logs:

2013-10-01 20:07:38,263 webhooks-http-retriever:thread-7 ERROR      [webhooks.util.http.CachingHttpContentRetriever] Unable to post to http://XXX.XX.XX.XXX:8080 due to HTTP/1.0 407 Proxy Authentication Required

Workaround

At this stage, the only known workaround is to configure the Proxy Server to allow non-authenticated requests. You may be able to limit the incoming connections by network address, or through another method.