elastic / elastic/logstash

management doesn't require SSL connection with elasticsearch

Open
#9,442 0 comments 0 reactions 0 assignees View on GitHub
management v6.0.0-rc1 x-pack
Dominant language
Java
Stars
14.9k
Forks
3.5k
Avg merge
1d 4h
Merged PRs (30d)
88

Description

*Original comment by @jsvd:*

setting the following in the config/logstash.yml makes management work without having to set SSL, which I think can be a security concern as the configs (with their passwords) will travel in plain text:

```
xpack.management.enabled: true
xpack.management.elasticsearch.username: elastic
xpack.management.elasticsearch.password: elastic
xpack.management.elasticsearch.url: "http://localhost:9200"
```

while the x-pack logstash should force this, there should be something on the elasticsearch side also rejecting management commands unless they come from a secure connection?

Contributor guide

Open the contributing guide

Research direction

Start with the config/logstash.yml settings and the x-pack Logstash management path named in the issue, then trace how the Elasticsearch URL and credentials are handled. Investigate the proposed Elasticsearch-side rejection of insecure management connections; done means management commands cannot use plain HTTP without a secure-connection failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch
Domain
security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.