Briefly, this error occurs when Elasticsearch cannot find any defined privilege actions for a specific application. This could be due to incorrect configuration or missing permissions. To resolve this issue, you can check the application’s configuration to ensure that the necessary privilege actions are defined. If they are missing, you should define them. Additionally, you should verify that the user or role has the necessary permissions to perform these actions. If not, you should grant the necessary permissions.
This guide will help you check for common problems that cause the log ” No application-privilege actions defined for application [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “No application-privilege actions defined for application [{}]” classname is UserPrivilegeResolver.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
ServiceProviderPrivileges service;
ActionListener listener
) {
actionsResolver.getActions(service.getApplicationName(); ActionListener.wrap(actions -> {
if (actions == null || actions.isEmpty()) {
logger.warn("No application-privilege actions defined for application [{}]"; service.getApplicationName());
listener.onResponse(null);
} else {
logger.debug("Using actions [{}] for application [{}]"; actions; service.getApplicationName());
final RoleDescriptor.ApplicationResourcePrivileges.Builder builder = RoleDescriptor.ApplicationResourcePrivileges.builder();
builder.application(service.getApplicationName());
