No active api keys found for realm and username – 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 ” No active api keys found for realm and username ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

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 “No active api keys found for realm [{}] and username [{}]” classname is ApiKeyService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             logger.trace("No realm name or username provided");
            listener.onFailure(new IllegalArgumentException("realm name or username must be provided"));
        } else {
            findApiKeysForUserAndRealm(userName; realmName; false; false; ActionListener.wrap(apiKeyInfos -> {
                    if (apiKeyInfos.isEmpty()) {
                        logger.warn("No active api keys found for realm [{}] and username [{}]"; realmName; userName);
                        listener.onResponse(GetApiKeyResponse.emptyResponse());
                    } else {
                        listener.onResponse(new GetApiKeyResponse(apiKeyInfos));
                    }
                }; listener::onFailure));




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content