-
Notifications
You must be signed in to change notification settings - Fork 306
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
empty password causes logstash to crash #614
Comments
Another way to trigger:
The code responsible for this comes from the default = nil if default.is_a?(String) && default.empty? # Blanks are as good as nil
uri_value = nil if uri_value.is_a?(String) && uri_value.empty? |
I was only able to reproduce this on Logstash 5.5.0, but not 5.6 nor 6.2.4. The latter two both react as expected by logging 401s, when either the password option is an empty string, or when the user:pass are specified in a host (with an empty pass). In other words, this works in both supported versions. Should we actually just close this as won't fix, since the 5.x line is no longer affected? |
Note, however, that I do not have a user without a password. X-Pack doesn't let me create one. Is a situation where the passwordless user is in fact a reverse proxy user (e.g. an http auth user in nginx)? |
configuration example:
result:
The text was updated successfully, but these errors were encountered: