Briefly, this error occurs when you try to invalidate an API key in Elasticsearch, but no active keys exist for the specified realm and username. This could be due to the key already being invalidated or deleted, or the key never existed. To resolve this, ensure that the API key you’re trying to invalidate is active and valid. If the key is already invalidated or deleted, no action is needed. If you’re unsure, you can list all API keys for a user to verify. Always double-check the realm and username for typos or case-sensitivity issues.
This guide will help you check for common problems that cause the log ” No active api keys to invalidate for realm [{}] and username [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “No active api keys to invalidate 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");
invalidateListener.onFailure(new IllegalArgumentException("realm name or username must be provided"));
} else {
findApiKeysForUserAndRealm(userName; realmName; true; false; ActionListener.wrap(apiKeyIds -> {
if (apiKeyIds.isEmpty()) {
logger.warn("No active api keys to invalidate for realm [{}] and username [{}]"; realmName; userName);
invalidateListener.onResponse(InvalidateApiKeyResponse.emptyResponse());
} else {
invalidateAllApiKeys(apiKeyIds.stream().map(apiKey -> apiKey.getId()).collect(Collectors.toSet()); invalidateListener);
}
}; invalidateListener::onFailure));
