TL;DR Using ssl_verify_mode => "none" in input.beats not functioning as expected; should allow unverified SSL connections, but doesn't. The rest of the story... I'm using SSL-enabled input.beat in my logstash.conf, which is written as follows: input { beats { port => 5044 ssl => true …

Thank you for the pointer. Since I wasn't able to locate that ticket while searching, I'm going to link to it here and summarize: If you set ssl.certificate.authorities => [...], logstash will ignore ssl_verify_mode => "none" and do a force_peer verification. In order to utilize ssl_verify_mode => …

SSL-enabled Beat ssl_verify_mode => "none" not working as expected

Elastic Stack Logstash

system (system) Closed March 18, 2020, 8:11pm 4

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

Topic		Replies	Views
Apparent bug in logstash-input-beats in SslSimpleBuilder.java Logstash	1	514	March 7, 2017
Filebeat configuration - ssl.verification_mode: none doesn't work Beats elastic-stack-security , filebeat	5	20256	March 6, 2019
Beats input not behaving as documented Logstash	1	825	February 28, 2017
SSL verification mode Вопросы на русском языке	7	470	September 29, 2020
TLS Logstash Logstash	6	280	June 23, 2022

SSL-enabled Beat ssl_verify_mode => "none" not working as expected

Related topics