Briefly, this error occurs when a user successfully authenticates to Elasticsearch using the REST API. It’s not an error, but an informational message indicating that the authentication process was successful. If you don’t want to see these messages, you can adjust the logging level in Elasticsearch to exclude informational messages. Alternatively, you can configure the security settings to disable detailed authentication logs. However, these logs can be useful for troubleshooting and auditing, so consider the implications before making changes.
This guide will help you check for common problems that cause the log ” {}[rest] [authentication_success]\t{}; {}; realm=[{}]; uri=[{}]; params=[{}]{}; request_body=[{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “{}[rest] [authentication_success]\t{}; {}; realm=[{}]; uri=[{}]; params=[{}]{}; request_body=[{}]” classname is DeprecatedLoggingAuditTrail.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
@Override
public void authenticationSuccess(String requestId; String realm; User user; RestRequest request) {
if (events.contains(AUTHENTICATION_SUCCESS) && (eventFilterPolicyRegistry.ignorePredicate()
.test(new AuditEventMetaInfo(Optional.of(user); Optional.of(realm); Optional.empty(); Optional.empty())) == false)) {
if (includeRequestBody) {
logger.info("{}[rest] [authentication_success]\t{}; {}; realm=[{}]; uri=[{}]; params=[{}]{}; request_body=[{}]";
localNodeInfo.prefix; hostAttributes(request); principal(user); realm; request.uri(); request.params(); opaqueId();
restRequestContent(request));
} else {
logger.info("{}[rest] [authentication_success]\t{}; {}; realm=[{}]; uri=[{}]; params=[{}]{}"; localNodeInfo.prefix;
hostAttributes(request); principal(user); realm; request.uri(); request.params(); opaqueId());
