Briefly, this error occurs when Elasticsearch receives a request that requires secondary authentication, but it is not provided. This could be due to incorrect configuration of security settings or missing credentials. To resolve this, ensure that the necessary authentication details are included in your request. Alternatively, check your Elasticsearch security settings to ensure that they are correctly configured to require secondary authentication only when necessary. If you’re using an API key for authentication, ensure it has the necessary permissions.
This guide will help you check for common problems that cause the log ” Request is missing secondary authentication ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, request.
Log Context
Log “Request is missing secondary authentication” class name is TransportSamlInitiateSingleSignOnAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
possiblyReplyWithSamlFailure(
authenticationState;
request.getSpEntityId();
request.getAssertionConsumerService();
StatusCode.REQUESTER;
new ElasticsearchSecurityException("Request is missing secondary authentication"; RestStatus.FORBIDDEN);
listener
);
return;
}
buildUserFromAuthentication(secondaryAuthentication; sp; ActionListener.wrap(user -> {
