# Configure Proxy Settings in Kibana to access Webhook
**URL:** https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604
**Category:** Kibana
**Tags:** elastic-stack-alerting
**Created:** [January 17, 2022, 4:09pm UTC](https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604 "2022-01-17T16:09:29Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@mralladin](https://discuss.elastic.co/u/mralladin)
#### Post date: [January 17, 2022, 4:09pm UTC](https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604/1 "2022-01-17T16:09:29Z")
Hello I want to send Alerts via Webhook to the Webex Api but the Kibana/Elastic Application ist behind our Company Proxy.
I tried already with
> xpack.actions.proxyUrl: "[http://TechnicalUser:Password@Proxy](http://TechnicalUser:Password@Proxy):Port"
> But it seems not to authenticate and I did also not find any other proxy configuration where I can set a Technical User and Password to let Kibana authenticate at our proxy.
Somebody have an idea?
Thank you very much,
Phil
---
### Author:  [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)
#### Post date: [January 18, 2022, 2:06pm UTC](https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604/2 "2022-01-18T14:06:52Z")
Were there errors in the Kibana logs? What do you see in the Kibana UI when you use the "test" page of the connector? What version of the stack are you using? Are you using this proxy with other programs, and if so, what value are you using for the proxy (usually some `*PROXY*` environment variable)?
There are a number of proxy-related config variables for connectors, documented here: [Alerting and action settings in Kibana | Kibana Guide [7.16] | Elastic](https://www.elastic.co/guide/en/kibana/current/alert-action-settings-kb.html#action-settings) - I wonder if one of those could be relevant to you.
---
### Author:  [@mralladin](https://discuss.elastic.co/u/mralladin)
#### Post date: [January 18, 2022, 3:04pm UTC](https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604/3 "2022-01-18T15:04:45Z")
I get the error web socket close. On our Proxy we just see there is proxy access without auhtorization so it gets blocked.
---
### Author:  [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)
#### Post date: [January 18, 2022, 5:53pm UTC](https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604/4 "2022-01-18T17:53:16Z")
Looking at the code briefly, it appears we are likely only using the hostname, port and protocol from the `proxyUrl` settings, when constructing the info for the proxy. We do have a separate config `xpack.actions.proxyHeaders` which I believe you could use to pass the Authentication header. You'll need to do the base64 encoding on the value ... [Basic access authentication - Wikipedia](https://en.wikipedia.org/wiki/Basic_access_authentication#Client_side)
---
### Author:  [@mralladin](https://discuss.elastic.co/u/mralladin)
#### Post date: [January 20, 2022, 4:02pm UTC](https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604/5 "2022-01-20T16:02:17Z")
> [@Patrick\_Mueller](#):
>
> xpack.actions.proxyHeaders
Hello Patrick thanks for the info. How you would deliver in this case the Header because my Kibana is not starting anymore if I deliver like the following:
```auto
xpack.actions.proxyHeaders: {Authorization: Basic BASE64Here}
or
xpack.actions.proxyHeaders: {"Authorization: Basic BASE64Here"}
or
xpack.actions.proxyHeaders: [Authorization: Basic BASE64Here]
or
xpack.actions.proxyHeaders:
Authorization: Basic Basic BASE64Here
```
With the last the Kibana is starting but not sending Authorization Credentials to the proxy.
Unfortunately there is no documentation/example about this.
---
### Author:  [@mralladin](https://discuss.elastic.co/u/mralladin)
#### Post date: [January 25, 2022, 5:19pm UTC](https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604/6 "2022-01-25T17:19:36Z")
Maybe for an Update:
```auto
xpack.actions.proxyHeaders:
Authorization: 'Basic BASE64Here'
```
are not working because our Proxy only accepts NTLM Authentication.
Maybe somebody knows how to deliver this or is this even supported by elastic?
I did not find any similar topics to this issue.
Thanks
---
### Author:  [@mralladin](https://discuss.elastic.co/u/mralladin)
#### Post date: [February 4, 2022, 12:35pm UTC](https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604/7 "2022-02-04T12:35:37Z")
> [@Patrick\_Mueller](#):
>
> s we are likely only using the hostname, port and protocol from the `proxyUrl` settings, when constructing the info for the proxy. We do have a separate config `xpack.actions.proxyHeaders` which I believe you could use to pass the A
Could you atleast tell if Elastic implement in the future maybe ntlm support? So people who are behind a NTLM Company Proxy can use Webhooks to external Apis like Webex ?
---
### Author:  [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)
#### Post date: [February 4, 2022, 1:56pm UTC](https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604/8 "2022-02-04T13:56:24Z")
I'm not seeing any current Kibana issues open for NTLM proxy support. Feel free to open an issue against Kibana for this: [https://github.com/elastic/kibana/issues/new?assignees=&labels=&template=Feature\_request.md](https://github.com/elastic/kibana/issues/new?assignees=&labels=&template=Feature_request.md)
After you create it, respond back here with the issue link and I'll get it tagged appropriately ...
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 4, 2022, 1:57pm UTC](https://discuss.elastic.co/t/configure-proxy-settings-in-kibana-to-access-webhook/294604/9 "2022-03-04T13:57:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.