Briefly, this error occurs when the Elasticsearch Exporter is configured with both ‘auth secure password’ and ‘auth password’. This is a conflict because only one method of authentication should be specified. To resolve this issue, you should choose one method of authentication. If you want to use ‘auth secure password’, remove the ‘auth password’ from your configuration and vice versa. Ensure that the chosen method is correctly configured and matches the authentication method set up in your Elasticsearch cluster.
This guide will help you check for common problems that cause the log ” exporter [{}] specified both auth.secure_password and auth.password. using auth.secure_password and ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “exporter [{}] specified both auth.secure_password and auth.password. using auth.secure_password and ” classname is HttpExporter.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final SecureString securePassword = SECURE_AUTH_PASSWORDS.get(config.name());
final String password;
if (securePassword != null) {
password = securePassword.toString();
if (Strings.isNullOrEmpty(deprecatedPassword) == false) {
logger.warn("exporter [{}] specified both auth.secure_password and auth.password. using auth.secure_password and " +
"ignoring auth.password"; config.name());
}
} else {
password = deprecatedPassword;
}
