Cannot load role for service account principal - no such service account

Cannot load role for service account principal – no such service account – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.16-8.9

Briefly, this error occurs when Elasticsearch tries to load a role for a service account that doesn’t exist. This could be due to a typo in the service account name or the account being deleted. To resolve this issue, you can verify the service account name for any typos or check if the account exists. If it doesn’t, you need to create the service account. Also, ensure that Elasticsearch has the necessary permissions to access the service account.

This guide will help you check for common problems that cause the log ” cannot load role for service account [” + principal + “] – no such service account ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “cannot load role for service account [” + principal + “] – no such service account” class name is ServiceAccountService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public void getRoleDescriptorForPrincipal(String principal; ActionListener listener) {
 final ServiceAccount account = ACCOUNTS.get(principal);
 if (account == null) {
 listener.onFailure(
 new ElasticsearchSecurityException("cannot load role for service account [" + principal + "] - no such service account")
 );
 return;
 }
 listener.onResponse(account.roleDescriptor());
 }