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

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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 [{}]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

WatcherXContentParser watcherParser = (WatcherXContentParser) parser;
 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));


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content