Found redacted password in field – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch detects sensitive data, such as a password, in a field that should not contain such information. This is a security measure to prevent unauthorized access. To resolve this issue, you can either remove the sensitive data from the field or encrypt the data before storing it. Additionally, you should review your data input processes to ensure sensitive data is not being inadvertently included in inappropriate fields.

This guide will help you check for common problems that cause the log ” found redacted password in field [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “found redacted password in field [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (parser instanceof WatcherXContentParser watcherParser) {
 if (REDACTED_PASSWORD.equals(text)) {
 if (watcherParser.allowRedactedPasswords) {
 return null;
 } else {
 throw new ElasticsearchParseException("found redacted password in field [{}]"; parser.currentName());
 } else if (watcherParser.cryptoService != null) {
 return new Secret(watcherParser.cryptoService.encrypt(chars));


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?