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

Average Read Time

2 Mins

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

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Check-Up which can resolve issues that cause many errors.

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: repositories, azure, repository-azure and plugins.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

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

private static String buildConnectString(String account; @Nullable String key; @Nullable String sasToken; String endpointSuffix) {
 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();

 

Watch a demo of the Check-Up:

Analyze your cluster