# XPack Watches + HTTP INput + Mutual Auth
**URL:** https://discuss.elastic.co/t/xpack-watches-http-input-mutual-auth/181915
**Category:** Elasticsearch
**Created:** [May 21, 2019, 12:28am UTC](https://discuss.elastic.co/t/xpack-watches-http-input-mutual-auth/181915 "2019-05-21T00:28:18Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)
#### Post date: [May 21, 2019, 12:28am UTC](https://discuss.elastic.co/t/xpack-watches-http-input-mutual-auth/181915/1 "2019-05-21T00:28:18Z")
Can we create Watches with REST http input that needs mutual auth certs?
---
### Author:  [@TimV](https://discuss.elastic.co/u/TimV)
#### Post date: [May 21, 2019, 1:08am UTC](https://discuss.elastic.co/t/xpack-watches-http-input-mutual-auth/181915/2 "2019-05-21T01:08:20Z")
Yes, you can (asusming you have a license that allows for the use of Watcher).
You need to configure this in the elasticsearch.yml configuration file by setting something like:
```auto
# Using a PKCS#12 keystore
xpack.http.ssl.keystore.path: path/to/keystore.p12
```
```auto
# Using PEM
xpack.http.ssl.certificate: path/to/cert.pem
xpack.http.ssl.key path/to/key.pem
```
There is only a single configuration that is applied to all watcher actions. I would recommend using a PKCS#12 keystore, as that will allow you to have multiple certificate+key pairs, and it should pick the correct certificate for the destination server.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 18, 2019, 1:08am UTC](https://discuss.elastic.co/t/xpack-watches-http-input-mutual-auth/181915/3 "2019-06-18T01:08:22Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.