graylog charm does not support authentication with elasticsearch

Bug #1758176 reported by Dmitrii Shcherbakov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Graylog Charm
Won't Fix
Wishlist
Unassigned

Bug Description

Currently graylog does not use any authentication mechanisms to prove its identity to elasticsearch.

See also:
https://bugs.launchpad.net/elasticsearch-charm/+bug/1758170

http://docs.graylog.org/en/2.4/pages/configuration/elasticsearch.html#graylog
"Optionally, you can also specify an authentication section containing a user name and a password, if either your Elasticsearch node uses Shield/X-Pack or Search Guard, or you have an intermediate HTTP proxy requiring authentication in between the Graylog server and the Elasticsearch node."

Tags: cpe-onsite
Paul Goins (vultaire)
Changed in graylog-charm:
importance: Undecided → Wishlist
status: New → Confirmed
Eric Chen (eric-chen)
Changed in charm-graylog:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.