rest realmauthenticationfailedtrealm= principal= uri= – How to solve related issues

rest realmauthenticationfailedtrealm= principal= uri= – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” rest realmauthenticationfailedtrealm= principal= uri= ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “{}[rest] [realm_authentication_failed]trealm=[{}]; {}; principal=[{}]; uri=[{}]{}” classname is DeprecatedLoggingAuditTrail.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             if (includeRequestBody) {
                logger.info("{}[rest] [realm_authentication_failed]\trealm=[{}]; {}; principal=[{}]; uri=[{}]{}; " + "request_body=[{}]";
                        localNodeInfo.prefix; realm; hostAttributes(request); token.principal(); request.uri(); opaqueId();
                        restRequestContent(request));
            } else {
                logger.info("{}[rest] [realm_authentication_failed]\trealm=[{}]; {}; principal=[{}]; uri=[{}]{}"; localNodeInfo.prefix;
                        realm; hostAttributes(request); token.principal(); request.uri(); opaqueId());
            }
        }
    }





 

Run the Check-Up to get a customized report like this:

Analyze your cluster