Log Security tokens are not available under the current license – How To Solve Related Issues


Log Security tokens are not available under the current license – How To Solve Related Issues

Opster Team

Jan-20, 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 that cause many errors.

This guide will help you check for common problems that cause the log ” Security tokens are not available under the current license ” 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: handler, license, plugin and rest.

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 pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log “Security tokens are not available under the current [{}] license” classname is TokenBaseRestHandler.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         if (failedFeature != null) {
            return failedFeature;
        } else if (licenseState.isTokenServiceAllowed()) {
            return null;
        } else {
            logger.info("Security tokens are not available under the current [{}] license"; licenseState.getOperationMode().description());
            return LicenseUtils.newComplianceException("security tokens");
        }
    }
}





 

Optimize Elasticsearch Performance

Try The Tool