# Kibana configuration and cookie based authentication

**URL:** <https://discuss.elastic.co/t/kibana-configuration-and-cookie-based-authentication/17208>\
**Category:** Elasticsearch\
**Created:** [April 25, 2014, 8:43pm UTC](https://discuss.elastic.co/t/kibana-configuration-and-cookie-based-authentication/17208 "2014-04-25T20:43:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Booker\_Bense](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/booker_bense/32/1618_2.png) [@Booker\_Bense](https://discuss.elastic.co/u/Booker_Bense)\
**Post date:** [April 25, 2014, 8:43pm UTC](https://discuss.elastic.co/t/kibana-configuration-and-cookie-based-authentication/17208/1 "2014-04-25T20:43:02Z")

</div>

I'm attempting to share a dashboard with the rest of my group and I'm  
running into problems where kibana  
can not access the es proxy.

The proxy is behind a cookie based authentication system.

Kibana complains that it can't find \_nodes

It is configured to use

elasticsearch: "[https://server.my.domain:443/es](https://server.my.domain:443/es)"

However, from Chrome and other browsers, I can access es just fine and in  
particular this works.

[https://server.my.domain/es/\_nodes](https://server.my.domain/es/_nodes)

My guess is that somehow I need to get kibana to forward the appropriate  
cookies. I've tried changing the  
line to

elasticsearch: { server:"[https://server.my.domain:443/es](https://server.my.domain:443/es)",  
with-credentials : true }

but that did not help. I looked at the logs on the elasticsearch proxy host  
and it appears that  
kibana is not even querying it. Any suggestion about where to start looking  
would be appreciated.

thanks,

- Booker C. Bense

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/81ca6a34-d175-4ac1-9a87-f8841f419453%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/81ca6a34-d175-4ac1-9a87-f8841f419453%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Booker\_Bense](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/booker_bense/32/1618_2.png) [@Booker\_Bense](https://discuss.elastic.co/u/Booker_Bense)\
**Post date:** [April 25, 2014, 9:00pm UTC](https://discuss.elastic.co/t/kibana-configuration-and-cookie-based-authentication/17208/2 "2014-04-25T21:00:43Z")

</div>

I've just discovered the cookie is HttpOnly, so that is likely the  
fundamental problem.

- Booker C. Bense

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8b473bb7-d71a-4245-9b41-db7be0e5758d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8b473bb7-d71a-4245-9b41-db7be0e5758d%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 1:33am UTC](https://discuss.elastic.co/t/kibana-configuration-and-cookie-based-authentication/17208/3 "2017-07-06T01:33:26Z")

</div>