Authentication token does not have OpenID Connect 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.

This guide will help you check for common problems that cause the log ” Authentication token does not have OpenID Connect 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 token does not have OpenID Connect metadata [{}]”classname  is TransportOpenIdConnectLogoutAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

}
 } 
 private Object getFromMetadata(Map metadata; String key) {
 if (metadata.containsKey(key) == false) {
 throw new ElasticsearchSecurityException("Authentication token does not have OpenID Connect metadata [{}]"; key);
 }
 Object value = metadata.get(key);
 if (null != value && value instanceof String == false) {
 throw new ElasticsearchSecurityException(
 "In authentication token; OpenID Connect metadata [{}] is [{}] rather than " + "String";

 

See how you can use AutoOps to resolve issues


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Analyze your cluster & get personalized recommendations

Analyze Your Cluster
Or view the full platform AutoOps in action

Related Articles

Back to all articles
Skip to content