Briefly, this error occurs when a user or client tries to perform an action on Elasticsearch indices but lacks the necessary permissions. This is typically due to the user’s role not having the required privileges. To resolve this issue, you can either grant the necessary permissions to the user’s role or use a role that already has the required permissions. Alternatively, you can modify the Elasticsearch security settings to allow the action. However, be cautious with this approach as it may expose your Elasticsearch to potential security risks.
This guide will help you check for common problems that cause the log ” {}[transport] [run_as_denied]\t{}; {}; roles=[{}]; action=[{}]; indices=[{}]; 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_denied]\t{}; {}; roles=[{}]; action=[{}]; indices=[{}]; request=[{}]{}” classname is DeprecatedLoggingAuditTrail.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
if (eventFilterPolicyRegistry.ignorePredicate().test(new AuditEventMetaInfo(Optional.of(authentication.getUser());
Optional.of(effectiveRealmName(authentication)); Optional.of(authorizationInfo); indices)) == false) {
final LocalNodeInfo localNodeInfo = this.localNodeInfo;
final String[] roleNames = (String[]) authorizationInfo.asMap().get(LoggingAuditTrail.PRINCIPAL_ROLES_FIELD_NAME);
if (indices.isPresent()) {
logger.info("{}[transport] [run_as_denied]\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_denied]\t{}; {}; roles=[{}]; action=[{}]; request=[{}]{}"; localNodeInfo.prefix;
