# 3rd party auth Kibana cloud.elastic.co - cannot edit kibana.yml

**URL:** <https://discuss.elastic.co/t/3rd-party-auth-kibana-cloud-elastic-co-cannot-edit-kibana-yml/168499>\
**Category:** Kibana\
**Created:** [February 14, 2019, 11:45pm UTC](https://discuss.elastic.co/t/3rd-party-auth-kibana-cloud-elastic-co-cannot-edit-kibana-yml/168499 "2019-02-14T23:45:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![honzo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/honzo/32/40950_2.png) [@honzo](https://discuss.elastic.co/u/honzo)\
**Post date:** [February 14, 2019, 11:45pm UTC](https://discuss.elastic.co/t/3rd-party-auth-kibana-cloud-elastic-co-cannot-edit-kibana-yml/168499/1 "2019-02-14T23:45:15Z")

</div>

Hello, we are exploring the use of an OAuth proxy to grant login to Kibana using GitHub. We are using the ES Cloud offering.  
I started at [https://www.elastic.co/blog/user-impersonation-with-x-pack-integrating-third-party-auth-with-kibana](https://www.elastic.co/blog/user-impersonation-with-x-pack-integrating-third-party-auth-with-kibana), but am blocked already, because I cannot make the initial changes to `kibana.yml` in the User Settings Override. I get an error:

`'elasticsearch.requestHeadersWhitelist': is not allowed`

Browsing [https://www.elastic.co/guide/en/cloud/current/ec-manage-kibana-settings.html](https://www.elastic.co/guide/en/cloud/current/ec-manage-kibana-settings.html), sure enough that setting is not on the list.

Is there any other way to edit `kibana.yml` in the Cloud offering, or is this a limitation?

Thanks for any insight 🙂

Trevor

---

<div class="post-metadata">

**Author:** ![honzo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/honzo/32/40950_2.png) [@honzo](https://discuss.elastic.co/u/honzo)\
**Post date:** [February 15, 2019, 9:03pm UTC](https://discuss.elastic.co/t/3rd-party-auth-kibana-cloud-elastic-co-cannot-edit-kibana-yml/168499/2 "2019-02-15T21:03:47Z")

</div>

Had a quick reply on this from EC Support last night (thanks Chris!) .. it is a limitation of the SaaS, and it was recommended that we use SAML.  
[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)

SAML requires a Platinum license, but [Elastic.co](http://Elastic.co) does grant it's use as "a special gesture to startups and small business customers running clusters with less than 64 GB of memory" .. though there was some mention about needing a 2nd cluster to gain the features (which we have, for monitoring)  
[https://www.elastic.co/cloud/elasticsearch-service/subscriptions](https://www.elastic.co/cloud/elasticsearch-service/subscriptions)

Maybe this helps someone one day..

Trevor M

> **[spring.io](https://spring.io)**
>
> Let's build a better Enterprise. Spring helps development teams everywhere
> build simple, portable, fast and flexible JVM-based systems and applications.

---

<div class="post-metadata">

**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\
**Post date:** [February 18, 2019, 11:01pm UTC](https://discuss.elastic.co/t/3rd-party-auth-kibana-cloud-elastic-co-cannot-edit-kibana-yml/168499/3 "2019-02-18T23:01:06Z")

</div>

Hello,

Thanks a lot for keeping the community posted.

Cheers,  
Bhavya

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 18, 2019, 11:01pm UTC](https://discuss.elastic.co/t/3rd-party-auth-kibana-cloud-elastic-co-cannot-edit-kibana-yml/168499/4 "2019-03-18T23:01:09Z")

</div>

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