Neither a secret key nor a shared access token was set – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch is unable to authenticate a request due to missing security credentials. It’s expecting either a secret key or a shared access token, but neither has been provided. To resolve this issue, you can either set a secret key or a shared access token in your Elasticsearch configuration. Ensure that the credentials are correct and have the necessary permissions. If you’re using an access token, make sure it hasn’t expired. Also, check your application’s code to ensure it’s correctly passing these credentials when making requests to Elasticsearch.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Neither a secret key nor a shared access token was set. ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: azure, repository-azure, repositories.

Log Context

Log “Neither a secret key nor a shared access token was set.” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 @Nullable String secondaryEndpoint
 ) {
 final boolean hasSasToken = Strings.hasText(sasToken);
 final boolean hasKey = Strings.hasText(key);
 if (hasSasToken == false && hasKey == false) {
 throw new SettingsException("Neither a secret key nor a shared access token was set.");
 if (hasSasToken && hasKey) {
 throw new SettingsException("Both a secret as well as a shared access token were set.");
 final StringBuilder connectionStringBuilder = new StringBuilder();


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Get expert answers on Elasticsearch/OpenSearch