SAML in Elastic Cloud - Support cant fix and are saying its Consulting now!


(James Hogbin) #1

I've tried to implement the advice here on securing a Cloud Cluster with SAML

I added the following to the elasticsearch.yml being careful to use spaces rather than the tabs you get if you copy the example because YAML

There are spaces but the editor removes them in blockquotes
type: saml
order: 2
attributes.principal: "nameid:persistent"
attributes.groups: "groups"
idp.metadata.path: "[UUID]"
idp.entity_id: ""
sp.entity_id: "https:/[UUID]"
sp.acs: "https://[UUID]"
sp.logout: "https://[UUID]"

That didn't deploy with error > xpack is not allowed.

I also noticed the editor turns 4 x spaces into tabs so maybe that was the error anyway

I contacted support and they suggested I expand the YAML keys and it would work so I did saml 2 "nameid:persistent" "groups" "[UUID]" "" "https://[UUID]" "https://[UUID]" "https://[UUID]"

That didn't work either.

Elastic support are now saying this is NOT support but consulting!!!!

Has anybody got this to work at all? Am I doing something obviously dim?

(Thiago Souza) #2

The idp.entity_id in your realm config needs to match the entityID in the metadata file.

For more information, refer to Item 2 in

Cannot find metadata for entity [] in [metadata.xml]


(Dominik Weidenfeld) #3

I am having the same issue right now.
Is there already a solution for this, or do I have to contact the support as well?


(Ioannis Kakavas) #4

Hello Dominic,

Please open your own topic and share as much information as possible with details on what you have done, what is your current configuration and what is the error message that you are seeing. There is no bug we are aware of that needs to be resolved, this is apparently a configuration error.

(James Hogbin) #5


A couple of things.

  1. use the full path for the item you are configuring e.g.

< saml
< 2
< "nameid:persistent"
< "groups"
< "[uuid]"
< "[uuid]"
< "https://[uuid]"
< "https://[uuid]"
< "https://[uuid]"

  1. The needs to have the same value found in the html headers of the key

Browse to the metadata.path url and then view source. You should get something like...

<?xml version="1.0"?>
<EntityDescriptor xmlns="urn:oasis:names:tc:SAML:2.0:metadata" entityID="[UUID]">
<IDPSSODescriptor xmlns:ds="" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
<KeyDescriptor use="signing">
<ds:KeyInfo xmlns:ds="">
<ds:X509Data> ... ...

In my case both the entity_id and the metadata_path are the same.

(James Hogbin) #6

Also the key: "nameid:persistent"

means you need to use a NameID (persistent) app

(Ioannis Kakavas) #7

A few comments in case this is helpful to others:

The configuration parameter needs to be the same as the Entity ID of the SAML IdP you are using. One way to figure this out is to look at the metadata, as @hogbinj suggests or look at the configuration pages of your IdP . Most have this shown in a prominent place in their UI or config.

This is actually the other way around. If your Identity Provider sets the SAML2 Name ID with a persistent format, or if you configure it to do so ( as @hogbinj is showing in his previous post ) then you need to configure Elasticsearch to read the value as such by setting: "nameid:persistent"

For detailed information on what this parameter is and what are other potential values, you can go through our documentation

(system) closed #8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.