# Watch actions proxy authentication

**URL:** <https://discuss.elastic.co/t/watch-actions-proxy-authentication/116894>\
**Category:** Elasticsearch\
**Created:** [January 24, 2018, 4:18pm UTC](https://discuss.elastic.co/t/watch-actions-proxy-authentication/116894 "2018-01-24T16:18:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcoward](https://avatars.discourse-cdn.com/v4/letter/j/4af34b/32.png) [@jcoward](https://discuss.elastic.co/u/jcoward)\
**Post date:** [January 24, 2018, 4:18pm UTC](https://discuss.elastic.co/t/watch-actions-proxy-authentication/116894/1 "2018-01-24T16:18:21Z")

</div>

I have been trying to get a watcher slack action to post a message to one of my workspace's channels. In the environment where the message must originate from there is a requirement to use a proxy server for egress to the the Slack provided webhook URL. While XPack does support the use of a proxy, either in the general settings or specified directly as fields in the watch itself, there does not seem to be a way to specify basic authentication via username and password to the proxy server, which is required in my environment. I attempted appending the username and password to the host, i.e username:password@host, but this simply returned a DNS lookup failure on the host name. Is their any way to authenticate with a proxy server when attempting to use actions associated with a watch?

Thanks

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 25, 2018, 8:23am UTC](https://discuss.elastic.co/t/watch-actions-proxy-authentication/116894/2 "2018-01-25T08:23:25Z")

</div>

Hey Joshua,

this is not currently supported. I will raise an internal issue, but cannot do any promises when we will add support for this.

--Alex

---

<div class="post-metadata">

**Author:** ![jcoward](https://avatars.discourse-cdn.com/v4/letter/j/4af34b/32.png) [@jcoward](https://discuss.elastic.co/u/jcoward)\
**Post date:** [January 27, 2018, 10:20pm UTC](https://discuss.elastic.co/t/watch-actions-proxy-authentication/116894/3 "2018-01-27T22:20:15Z")

</div>

Alex,  
Thanks for the reply. I appreciate you taking the action to raise an internal issue. In the interim, we will attempt to find a workaround. I may be able to get our Elastic stack whitelisted in the proxy to allow egress without authentication.

Josh

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 24, 2018, 10:20pm UTC](https://discuss.elastic.co/t/watch-actions-proxy-authentication/116894/4 "2018-02-24T22:20:17Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.