Security tokens are not enabled – Elasticsearch Error How To Solve Related Issues



Security tokens are not enabled – 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 “security tokens are not enabled” 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: plugin.


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”security tokens are not enabled”classname  is TokenService.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (licenseState.isSecurityEnabled() == false ||
  licenseState.checkFeature(XPackLicenseState.Feature.SECURITY_TOKEN_SERVICE) == false) {
  throw LicenseUtils.newComplianceException("security tokens");
  }
  if (enabled == false) {
  throw new FeatureNotEnabledException(Feature.TOKEN_SERVICE; "security tokens are not enabled");
  }
  }
 
  /**
  * In version {@code #VERSION_TOKENS_INDEX_INTRODUCED} security tokens were moved into a separate index; away from the other entities in

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 OAuth Token API Not Working In Elastic Search -views 62 ,score 1

OAuth Token API Not Working In Elastic Search Even Security Disabled -views   57,score 2



Find Configuration Errors

Analyze Now