Rest anonymous access denied t uri= – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-6.8

Briefly, this error occurs when an anonymous user tries to access a resource in Elasticsearch without the necessary permissions. This could be due to incorrect configuration settings or a lack of authentication. To resolve this issue, you can either provide the necessary permissions to the anonymous user or set up proper authentication. You can also disable anonymous access if it’s not required. Additionally, ensure that the URI is correct and accessible.

This guide will help you check for common problems that cause the log ” {}[rest] [anonymous_access_denied]t{}; uri=[{}]{} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

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

                 && (eventFilterPolicyRegistry.ignorePredicate().test(AuditEventMetaInfo.EMPTY) == false)) {
            if (includeRequestBody) {
                logger.info("{}[rest] [anonymous_access_denied]\t{}; uri=[{}]{}; request_body=[{}]"; localNodeInfo.prefix;
                        hostAttributes(request); request.uri(); opaqueId(); restRequestContent(request));
            } else {
                logger.info("{}[rest] [anonymous_access_denied]\t{}; uri=[{}]{}"; localNodeInfo.prefix; hostAttributes(request);
                        request.uri(); opaqueId());
            }
        }
    }





 

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?