Briefly, this error occurs when a user tries to access a service in Elasticsearch for which they don’t have the necessary permissions. This could be due to incorrect user roles or privileges. To resolve this issue, you can check the user’s assigned roles and permissions in the Elasticsearch security settings. If necessary, you can modify the user’s roles to include the required permissions for the service they’re trying to access. Alternatively, you can create a new role with the necessary permissions and assign it to the user.
This guide will help you check for common problems that cause the log ” User [{}] is not permitted to access service [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “User [{}] is not permitted to access service [{}]” class name is TransportSamlInitiateSingleSignOnAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
buildUserFromAuthentication(secondaryAuthentication; sp; ActionListener.wrap(
user -> {
if (user == null) {
possiblyReplyWithSamlFailure(authenticationState; request.getSpEntityId();
request.getAssertionConsumerService(); StatusCode.REQUESTER;
new ElasticsearchSecurityException("User [{}] is not permitted to access service [{}]";
RestStatus.FORBIDDEN; secondaryAuthentication.getUser().principal(); sp.getEntityId());
listener);
return;
}
final SuccessfulAuthenticationResponseMessageBuilder builder =
