Security tokens are not enabled – 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 Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” security tokens are not enabled ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “security tokens are not enabled”classname  is 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


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content