elastic/logstash

elasticsearch connection produces 401 when password contains certain characters.

Open

#11,193 opened on Oct 4, 2019

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Ruby (14,197 stars) (3,496 forks)batch import
buggood first issue

Description

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.

Contributor guide

Tech stack
rubyelasticsearch
Domain
backendapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
understanding of HTTP basic authURL encoding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
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.