Briefly, this error occurs when Elasticsearch is trying to execute an action that requires certain roles or permissions, but the current user or process doesn’t have the necessary permissions. This could be due to incorrect configuration of user roles or security settings. To resolve this issue, you can check and update the user roles to ensure they have the necessary permissions. Alternatively, you can modify the security settings to allow the action to be executed. Also, ensure that the Elasticsearch cluster is properly configured and running with the correct security settings.
This guide will help you check for common problems that cause the log ” {}[transport] [run_as_granted]\t{}; {}; roles=[{}]; action=[{}]; request=[{}]{} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “{}[transport] [run_as_granted]\t{}; {}; roles=[{}]; action=[{}]; request=[{}]{}” classname is DeprecatedLoggingAuditTrail.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
logger.info("{}[transport] [run_as_granted]\t{}; {}; roles=[{}]; action=[{}]; indices=[{}]; request=[{}]{}";
localNodeInfo.prefix; originAttributes(threadContext; message; localNodeInfo); runAsSubject(authentication);
arrayToCommaDelimitedString(roleNames); action; arrayToCommaDelimitedString(indices.get());
message.getClass().getSimpleName(); opaqueId());
} else {
logger.info("{}[transport] [run_as_granted]\t{}; {}; roles=[{}]; action=[{}]; request=[{}]{}"; localNodeInfo.prefix;
originAttributes(threadContext; message; localNodeInfo); runAsSubject(authentication);
arrayToCommaDelimitedString(roleNames); action; message.getClass().getSimpleName(); opaqueId());
}
}
}
[ratemypost]