# Logstash 5.6.3: TCP input - sslsubject no longer getting set

**URL:** https://discuss.elastic.co/t/logstash-5-6-3-tcp-input-sslsubject-no-longer-getting-set/103423
**Category:** Logstash
**Created:** [October 10, 2017, 7:13pm UTC](https://discuss.elastic.co/t/logstash-5-6-3-tcp-input-sslsubject-no-longer-getting-set/103423 "2017-10-10T19:13:55Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![utilitynerd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/utilitynerd/32/22944_2.png) [@utilitynerd](https://discuss.elastic.co/u/utilitynerd)
#### Post date: [October 10, 2017, 7:13pm UTC](https://discuss.elastic.co/t/logstash-5-6-3-tcp-input-sslsubject-no-longer-getting-set/103423/1 "2017-10-10T19:13:55Z")

</div>

I've run into an issue after upgrading to logstash 5.6.3

It seems that my TCP input, configured for TLS, is no longer setting the sslsubject field. If i downgrade back to 5.5.2, then sslsubject get correctly set again.

Here is my tcp input configuration:

tcp {  
port =\> 6514  
tags =\> ['syslog-tcp-tls']  
ssl\_verify =\> true  
ssl\_enable =\> true  
ssl\_cert =\> '/etc/logstash/logstash\_tls.cert'  
ssl\_key =\> '/etc/logstash/logstash\_tls.key.pk8'  
ssl\_extra\_chain\_certs =\> ['/etc/logstash/logstash\_tls.ca']  
}

Is anyone else experiencing this? I make extensive use of the sslsubject field to route logs and am eager to work this out.

---

<div class="post-metadata">

### Author: ![utilitynerd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/utilitynerd/32/22944_2.png) [@utilitynerd](https://discuss.elastic.co/u/utilitynerd)
#### Post date: [October 10, 2017, 10:02pm UTC](https://discuss.elastic.co/t/logstash-5-6-3-tcp-input-sslsubject-no-longer-getting-set/103423/2 "2017-10-10T22:02:52Z")

</div>

For anyone else running into this, it looks like this commit:

> <https://github.com/logstash-plugins/logstash-input-tcp/commit/e4d4510381b427de8476df82d63961e5031fd532#diff-4440c0d7ed519b24cf7f535409052e90>

broke sslsubject.

I've started an issue on the tcp-input github:

> <https://github.com/logstash-plugins/logstash-input-tcp/issues/89>

---

<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: [November 7, 2017, 10:03pm UTC](https://discuss.elastic.co/t/logstash-5-6-3-tcp-input-sslsubject-no-longer-getting-set/103423/3 "2017-11-07T22:03:07Z")

</div>

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