Failed to unmarshall SAML content – 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.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Failed to unmarshall SAML content ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Failed to unmarshall SAML content [{}]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

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());
 void print(Element element; Writer writer; boolean pretty) throws TransformerException {
 final Transformer serializer = getHardenedXMLTransformer();


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content