# Enrich logs with client certificate subject

**URL:** https://discuss.elastic.co/t/enrich-logs-with-client-certificate-subject/108698
**Category:** Logstash
**Created:** [November 22, 2017, 11:20am UTC](https://discuss.elastic.co/t/enrich-logs-with-client-certificate-subject/108698 "2017-11-22T11:20:26Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![cruscio](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cruscio/32/24562_2.png) [@cruscio](https://discuss.elastic.co/u/cruscio)
#### Post date: [November 22, 2017, 11:20am UTC](https://discuss.elastic.co/t/enrich-logs-with-client-certificate-subject/108698/1 "2017-11-22T11:20:26Z")

</div>

When Logstash is secured with SSL mutual authentication, is it possible to have Logstash add the client certificate's subject as a field in an event before forwarding to Elasticsearch?

---

<div class="post-metadata">

### Author: ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje)
#### Post date: [November 22, 2017, 3:41pm UTC](https://discuss.elastic.co/t/enrich-logs-with-client-certificate-subject/108698/2 "2017-11-22T15:41:43Z")

</div>

I don't think so. The SSL termination is negotiated well before the input ever receives the payload.

---

<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: [December 20, 2017, 3:41pm UTC](https://discuss.elastic.co/t/enrich-logs-with-client-certificate-subject/108698/3 "2017-12-20T15:41:58Z")

</div>

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