# Client certificate
**URL:** https://discuss.elastic.co/t/client-certificate/107617
**Category:** Beats
**Tags:** heartbeat
**Created:** [November 14, 2017, 7:58pm UTC](https://discuss.elastic.co/t/client-certificate/107617 "2017-11-14T19:58:23Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@zozo6015](https://discuss.elastic.co/u/zozo6015)
#### Post date: [November 14, 2017, 7:58pm UTC](https://discuss.elastic.co/t/client-certificate/107617/1 "2017-11-14T19:58:24Z")
Hello,
We have an api which needs to be checked by heartbeat but it needs client ssl authentication to get a proper 200 http code. Is there any way it could be configured?
Regards,
Peter
---
### Author:  [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [November 15, 2017, 2:40pm UTC](https://discuss.elastic.co/t/client-certificate/107617/2 "2017-11-15T14:40:20Z")
The [ssl settings](https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-heartbeat-options.html#monitor-http-tls-ssl) in the monitor do support all the ssl settings as available in the beats outputs. See [Specify SSL settings docs](https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-ssl.html) for available settings in the HTTP monitor.
Related docs bug report: [https://github.com/elastic/beats/issues/5599](https://github.com/elastic/beats/issues/5599)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 13, 2017, 2:40pm UTC](https://discuss.elastic.co/t/client-certificate/107617/3 "2017-12-13T14:40:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.