Security index does not exist therefore refresh token cannot be validated – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run 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 index does not exist therefore refresh token cannot be validated ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, plugin and refresh.

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 “Security index does not exist therefore refresh token [{}] cannot be validated” classname is TokenService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     .filter(QueryBuilders.termQuery("refresh_token.token"; refreshToken)))
                .setVersion(true)
                .request();
            final SecurityIndexManager frozenSecurityIndex = securityIndex.freeze();
            if (frozenSecurityIndex.indexExists() == false) {
                logger.warn("security index does not exist therefore refresh token [{}] cannot be validated"; refreshToken);
                listener.onFailure(invalidGrantException("could not refresh the requested token"));
            } else if (frozenSecurityIndex.isAvailable() == false) {
                logger.debug("security index is not available to find token from refresh token; retrying");
                attemptCount.incrementAndGet();
                findTokenFromRefreshToken(refreshToken; listener; attemptCount);




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content