Authentication did not contain metadata – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Authentication did not contain metadata ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: metadata, plugin.


 
 

metadata

Overview

Metadata in Elasticsearch refers to additional information stored for each document. This is achieved using the specific metadata fields available in Elasticsearch. The default behavior of some of these metadata fields can be customized during mapping creation.

Examples

Using _meta meta-field for storing application-specific information with the mapping:

PUT /my_index?pretty
{
  "mappings": {
    "_meta": { 
      "domain": "security",
      "release_information": {
        "date": "18-01-2020",
        "version": "7.5"
      }
    }
  }
}

Notes

  • In version 2.x, Elasticsearch had a total 13 meta fields available, which are: _index, _uid, _type, _id, _source, _size, _all, _field_names, _timestamp, _ttl, _parent, _routing, _meta
  • In version 5.x, _timestamp and _ttl meta fields were removed.
  • In version 6.x, the _parent meta field was removed.
  • In version 7.x, _uid and _all meta fields were removed.
 
 

plugins

 
 

Log Context

Log “Authentication did not contain metadata”classname  is TransportOpenIdConnectLogoutAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return ((OpenIdConnectRealm) realm).buildLogoutResponse(idToken);
 } 
 private void validateAuthenticationAndMetadata(Authentication authentication; Map tokenMetadata) {
 if (tokenMetadata == null) {
 throw new ElasticsearchSecurityException("Authentication did not contain metadata");
 }
 if (authentication == null) {
 throw new ElasticsearchSecurityException("No active authentication");
 }
 final User user = authentication.getUser();

 

"Opster not only stabilized and enhanced performance but also decreased our hardware expenses."

Matt Watson

CTO at Stackify

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Related Articles

Choose the Correct Number of Shards

How to Solve Indexing Downtime

Coupa Reduced Elasticsearch Costs by 60%

Skip to content