# Elastic Cloud does not apply kibana settings **URL:** \ **Category:** Kibana\ **Created:** [May 28, 2019, 6:59pm UTC](https://discuss.elastic.co/t/elastic-cloud-does-not-apply-kibana-settings/183168 "2019-05-28T18:59:09Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![leobaiano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leobaiano/32/43704_2.png) [@leobaiano](https://discuss.elastic.co/u/leobaiano)\ **Post date:** [May 28, 2019, 6:59pm UTC](https://discuss.elastic.co/t/elastic-cloud-does-not-apply-kibana-settings/183168/1 "2019-05-28T18:59:10Z")
I am following the documentation of the link below to activate the login with SAML in kibana however I always receive a message saying that the changes could not be applied. [https://www.elastic.co/guide/en/cloud/current/ec-securing-clusters-SAML.html](https://www.elastic.co/guide/en/cloud/current/ec-securing-clusters-SAML.html) The necessary changes in elasticsearch seem to be applied because it does not return any errors, but in kibana I can not. Has anyone ever experienced this? It does not have any details in the log, it says to try again and if the problem persists contact support. ![42](https://us1.discourse-cdn.com/elastic/original/3X/e/e/eeabca0b2ad40f5163dbe4eb35302397967a7508.png) ![10](https://us1.discourse-cdn.com/elastic/original/3X/1/5/1522b6c4cd184c0f1d3081eed79dd1e4098a62fe.png) ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [May 28, 2019, 8:11pm UTC](https://discuss.elastic.co/t/elastic-cloud-does-not-apply-kibana-settings/183168/2 "2019-05-28T20:11:23Z")
Do any either the ES or the Kibana logs in the logging and metrics cluster have any information? This is always an error in the SAML config which Kibana can't recover from I think Alex ---
**Author:** ![leobaiano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leobaiano/32/43704_2.png) [@leobaiano](https://discuss.elastic.co/u/leobaiano)\ **Post date:** [May 28, 2019, 8:31pm UTC](https://discuss.elastic.co/t/elastic-cloud-does-not-apply-kibana-settings/183168/3 "2019-05-28T20:31:05Z")
> [@Alex\_Piggott](#): > > Do any either the ES or the Kibana logs in the logging and metrics cluster have any information? I did not find where the kibana logs are and in elasticsearch I did not find anything relevant, just logs of success same. ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [May 28, 2019, 8:52pm UTC](https://discuss.elastic.co/t/elastic-cloud-does-not-apply-kibana-settings/183168/4 "2019-05-28T20:52:17Z")
Under the Kibana tab for a running deployment, there should be a link to the Kibana logs (under dashboard links maybe?) If you want to post a sanitized version of the ES and Kibana config, we can definitely comment on whether the issue looks like similar SAML gotchas we've seen in the past ---
**Author:** ![leobaiano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leobaiano/32/43704_2.png) [@leobaiano](https://discuss.elastic.co/u/leobaiano)\ **Post date:** [May 28, 2019, 9:15pm UTC](https://discuss.elastic.co/t/elastic-cloud-does-not-apply-kibana-settings/183168/5 "2019-05-28T21:15:03Z")
At the moment the updates were successfully made in kibana, I did not make any changes I just tried several times. It's redirecting correctly to the IdP inclusive, it looks fine, but it's weird having to have tried it several times. Below is the code I'm using in ES and Kibana. Where has xxxxxx I replace here. elasticsearch xpack: security: authc: realms: cloud-saml: type: saml order: 2 attributes.principal: "nameid:persistent" attributes.groups: "xxxxxxxx/groups" idp.metadata.path: "xxxxxxfederationmetadata.xml?appid=xxxxxx" idp.entity\_id: "xxxxxxxx/" sp.entity\_id: "[https://8b64c0c41ede48bc9e907a5279089109.us-east-1.aws.found.io:9243/](https://8b64c0c41ede48bc9e907a5279089109.us-east-1.aws.found.io:9243/)" sp.acs: "[https://8b64c0c41ede48bc9e907a5279089109.us-east-1.aws.found.io:9243/api/security/v1/saml](https://8b64c0c41ede48bc9e907a5279089109.us-east-1.aws.found.io:9243/api/security/v1/saml)" sp.logout: "[https://8b64c0c41ede48bc9e907a5279089109.us-east-1.aws.found.io:9243/logout](https://8b64c0c41ede48bc9e907a5279089109.us-east-1.aws.found.io:9243/logout)" kibana xpack.security.authProviders: [saml] server.xsrf.whitelist: [/api/security/v1/saml] xpack.security.public: protocol: https hostname: [8b64c0c41ede48bc9e907a5279089109.us-east-1.aws.found.io](http://8b64c0c41ede48bc9e907a5279089109.us-east-1.aws.found.io) port: 9243 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 11, 2019, 9:15pm UTC](https://discuss.elastic.co/t/elastic-cloud-does-not-apply-kibana-settings/183168/6 "2019-06-11T21:15:07Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.