Authentication token does not have OpenID Connect metadata – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.2-8.9

Briefly, this error occurs when Elasticsearch is unable to find the OpenID Connect metadata for the provided authentication token. This could be due to incorrect configuration of the OpenID Connect realm or the token being invalid. To resolve this issue, you can verify the configuration of your OpenID Connect realm in Elasticsearch, ensuring that the URLs and identifiers are correct. Additionally, check the validity of your token. If it’s expired or invalid, you’ll need to obtain a new one. Also, ensure that Elasticsearch can reach the OpenID Connect Provider’s metadata endpoint.

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: plugin, metadata.

 
 

plugins

 
 

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.
 
 

Log Context

Log “Authentication token does not have OpenID Connect metadata [{}]” class name is TransportOpenIdConnectLogoutAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }
 }  private static 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";

 

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?

Related Articles

Back to all articles