No api key ids provided for invalidation - Common causes and quick fixes

No api key ids provided for invalidation – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when an attempt is made to invalidate API keys in Elasticsearch without providing any API key IDs. This means that Elasticsearch doesn’t know which keys to invalidate. To resolve this issue, you should ensure that you provide the correct API key IDs when attempting to invalidate them. You can find these IDs in the response when you create the API keys. Alternatively, you can use the Get API Key API to retrieve the IDs of existing keys.

This guide will help you check for common problems that cause the log ” No api key ids provided for invalidation ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “No api key ids provided for invalidation” class name is ApiKeyService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 * @param listener  the listener to notify upon completion
 */
 private void indexInvalidation(Collection apiKeyIds; ActionListener listener) {
 maybeStartApiKeyRemover();
 if (apiKeyIds.isEmpty()) {
 listener.onFailure(new ElasticsearchSecurityException("No api key ids provided for invalidation"));
 } else {
 BulkRequestBuilder bulkRequestBuilder = client.prepareBulk();
 final long invalidationTime = clock.instant().toEpochMilli();
 for (String apiKeyId : apiKeyIds) {
 UpdateRequest request = client.prepareUpdate(SECURITY_MAIN_ALIAS; apiKeyId)

[ratemypost]