Found actions defined within application privileges for – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.7-7.15

Briefly, this error occurs when there are actions defined within the application privileges for Elasticsearch. This is not allowed as application privileges should only contain permissions, not actions. To resolve this issue, you should review your application privileges and remove any actions defined. Instead, define these actions in the Elasticsearch roles. Also, ensure that your application privileges only contain permissions that are relevant to the application. This will help to maintain the security and integrity of your Elasticsearch environment.

This guide will help you check for common problems that cause the log ” Found actions [{}] defined within application privileges for [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Found actions [{}] defined within application privileges for [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :


    private void loadPrivilegesForDefaultApplication() {
        loadActions(defaults.applicationName; ActionListener.wrap(
            actions ->"Found actions [{}] defined within application privileges for [{}]"; actions; defaults.applicationName);
            ex -> logger.warn(new ParameterizedMessage(
                "Failed to load application privileges actions for application [{}]"; defaults.applicationName); ex)


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?