In authentication token OpenID Connect metadata is rather than – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.2-7.15

Briefly, this error occurs when the OpenID Connect metadata in the authentication token does not match the expected value. This could be due to incorrect configuration or an issue with the OpenID provider. To resolve this, you can verify the OpenID Connect settings in Elasticsearch and ensure they match with your OpenID provider. Also, check the integrity of the authentication token. If the issue persists, consider resetting the token or contacting your OpenID provider for further assistance.

This guide will help you check for common problems that cause the log ” In authentication token; OpenID Connect metadata [{}] is [{}] rather than ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, metadata.

Log Context

Log “In authentication token; OpenID Connect metadata [{}] is [{}] rather than” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 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"; key; value.getClass());
 return value;  }


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?