Both a secret as well as a shared access token were 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 both a secret token and a shared access token are set in the Elasticsearch configuration. Elasticsearch requires only one type of token for authentication. To resolve this, you should remove either the secret token or the shared access token from the configuration. Ensure that the remaining token is correctly configured and has the necessary permissions. Restart Elasticsearch after making these changes.

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 ” Both a secret as well as a shared access token were 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 “Both a secret as well as a shared access token were set.” class name is AzureStorageSettings.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 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();
 connectionStringBuilder.append("DefaultEndpointsProtocol=https").append(";AccountName=").append(account);
 if (hasKey) {
 connectionStringBuilder.append(";AccountKey=").append(key);

 

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?