Both a secret as well as a shared access token were set. – Elasticsearch Error How To Solve Related Issues



Both a secret as well as a shared access token were set. – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

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

 

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. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: repositories, azure, repository-azure, plugins.


Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

Log Context

Log”Both a secret as well as a shared access token were set.”classname  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);

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Java ElasticSearch None of the configured nodes are available -views 142,496 ,score 58

AWS S3 – How to fix 'The request signature we calculated does not match the signature' error? -views   115,512,score 69



Find Configuration Errors

Analyze Now