elastic/logstash

elasticsearch connection produces 401 when password contains certain characters.

Open

#11,193 建立於 2019年10月4日

在 GitHub 查看
 (7 留言) (0 反應) (0 負責人)Ruby (14,197 star) (3,496 fork)batch import
buggood first issue

描述

I've only just started trying to use filebeat > logstash > elasticsearch (cloud) but having spent the day yesterday having problems I think I've found a potential bug. Apologies if the below is not in an acceptable format. Please note, I used a 14 day trail on Google for elasticsearch and kibana so I have no idea if this applies to on-prem/self-hosted variants.

  • Version: 7.4
  • Operating System: Windows
  • Config File (if you have sensitive info, please remove it):
  • Sample Data:
  • Steps to Reproduce:

Create a trail account with Google and when prompted/changing the password for the default elastic user, use a password containing the @ symbol.

Install Logstash and configure with cloud.id and cloud.auth as per trial account.

Run logstash and view log file. Logstash is unable to connect to elasticsearch due to a 401 error.

Back in elasticsearch, change the password for the elastic user so that it contains no @ symbols.

Amend the logstash configuration to use updated password and run. Elasticsearch connection should now work.

貢獻者指南

技術棧
rubyelasticsearch
領域
backendapi
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
understanding of HTTP basic authURL encoding
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Investigate how Logstash constructs the HTTP Basic Auth header or URL for Elasticsearch cloud connections. The issue likely stems from the password not being URL encoded when containing special characters like '@'. Look at the code responsible for parsing the cloud.auth configuration and forming the HTTP request, possibly in the Elasticsearch output plugin.