SAML object is incorrect type Expected but was – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.7-8.9

Briefly, this error occurs when the Security Assertion Markup Language (SAML) object type doesn’t match the expected type in Elasticsearch. This could be due to incorrect configuration or data type mismatch. To resolve this, you should first verify your SAML configuration settings. Ensure that the object types align with what Elasticsearch expects. If the issue persists, check the data types of the objects you’re working with. They should match the expected data types in your SAML configuration.

This guide will help you check for common problems that cause the log ” SAML object [{}] is incorrect type. Expected [{}] but was [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “SAML object [{}] is incorrect type. Expected [{}] but was [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 final XMLObject object = unmarshaller.unmarshall(element);
 if (type.isInstance(object)) {
 return type.cast(object);
 Object[] args = new Object[] { element.getTagName(); type.getName(); object.getClass().getName() };
 throw new ElasticsearchSecurityException("SAML object [{}] is incorrect type. Expected [{}] but was [{}]"; args);
 } catch (UnmarshallingException e) {
 throw new ElasticsearchSecurityException("Failed to unmarshall SAML content [{}]"; e; element.getTagName());