Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide option to disable SSL hostname verification #49

Closed
n0othing opened this issue Oct 12, 2016 · 4 comments · Fixed by #168
Closed

Provide option to disable SSL hostname verification #49

n0othing opened this issue Oct 12, 2016 · 4 comments · Fixed by #168

Comments

@n0othing
Copy link

Currently, there is no option to disable hostname verification when connection to an cluster with SSL enabled.

https://www.elastic.co/guide/en/logstash/current/plugins-filters-elasticsearch.html#_synopsis_119

While insecure (and should not be used for production), it would be nice to allow a configuration option to disable hostname verification for testing/debug purposes. This is similar to the logstash-output-elasticsearch which exposes such an option.

@MohMaz
Copy link

MohMaz commented Dec 27, 2016

+1

@jordansissel
Copy link
Contributor

Please don't disable SSL verification. If you don't want security, please turn SSL off on your cluster.

@nithril
Copy link

nithril commented Jul 27, 2018

Elasticsearch default way of generating node certificates does not include the hostname. Instead it is based on a CA.

To not be able to disable hostname verification is not compatible with the elasticsearch documentation.

@nicenemo
Copy link

nicenemo commented Apr 7, 2022

Since Version 8 Elastic provides a nice docker-compose.yml which generates certificates an puts elasticsearch on https://. Awesome!
The Logstash Elasticsearch input/output plugin do have an option to disable certificate checking. The filter plugin does not.
That is not consistent.

Please either make it consistent by:

  • Removing this option from the input/output plugin and provide some glue to use the certificate generated by the docker-compose with Logstash not running in Docker.

  • Or just add this option to the Elasticsearch filter plugin too.

    Not having this option on the filter plugin surprised me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants