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.

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";

 

 [ratemypost]