# SOLVED: ES using AD Authentication crashes when logged in through Kibana

**URL:** <https://discuss.elastic.co/t/solved-es-using-ad-authentication-crashes-when-logged-in-through-kibana/68733>\
**Category:** Elasticsearch\
**Created:** [December 12, 2016, 4:07pm UTC](https://discuss.elastic.co/t/solved-es-using-ad-authentication-crashes-when-logged-in-through-kibana/68733 "2016-12-12T16:07:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Terence\_Earl\_Michael](https://avatars.discourse-cdn.com/v4/letter/t/258eb7/32.png) [@Terence\_Earl\_Michael](https://discuss.elastic.co/u/Terence_Earl_Michael)\
**Post date:** [December 12, 2016, 4:07pm UTC](https://discuss.elastic.co/t/solved-es-using-ad-authentication-crashes-when-logged-in-through-kibana/68733/1 "2016-12-12T16:07:51Z")

</div>

Hi,

I'm experiencing an interesting issue, whereby I have configured both native and active directory authentication to Elasticsearch - I can log in with both an AD user and a native user to Kibana and can view all data in all indexes with my two users - when I choose to open a dashboard however, the native user works fine but the AD user causes the elasticsearch process to hang which must be forcibly killed - I cannot connect to port 9200 and obviously Kibana does not pull out any data.

I have increased Heap memory to 2GB, but I can't work out why native user would behave as expected... Any help would be appreciated!

elasticsearch.yml details below (I have masked some company specific data):

network.host: 0.0.0.0  
xpack:  
security:  
authc:  
realms:  
native1:  
type: native  
order: 0  
active\_directory:  
type: active\_directory  
order: 1  
domain\_name: **.**  
url: ldaps:// **.**.\***_:636  
unmapped\_groups\_as\_roles: true  
ssl:  
certificate\_authorities: E:\Logstash\elasticsearch\config\x-pack\*_**.pem

---

<div class="post-metadata">

**Author:** ![Terence\_Earl\_Michael](https://avatars.discourse-cdn.com/v4/letter/t/258eb7/32.png) [@Terence\_Earl\_Michael](https://discuss.elastic.co/u/Terence_Earl_Michael)\
**Post date:** [December 12, 2016, 5:15pm UTC](https://discuss.elastic.co/t/solved-es-using-ad-authentication-crashes-when-logged-in-through-kibana/68733/2 "2016-12-12T17:15:01Z")

</div>

EDIT: While writing this I found the problem: The setting unmapped\_groups\_as\_roles: true in the elasticsearch.yml caused the problem. I don't know why this happened, but after setting it to false, everything works like expected.

This is the same issue as found by another user - I promise I searched for the issue in existing topics, but it was typical that the I found another thread 30 mins after posting my own (I even stole his edit - apologies and credit to nick.e [Performance Issues and timeouts with Elasticsearch](https://discuss.elastic.co/t/performance-issues-and-timeouts-with-elasticsearch/67008/2))

---

<div class="post-metadata">

**Author:** ![nick.e](https://avatars.discourse-cdn.com/v4/letter/n/8dc957/32.png) [@nick.e](https://discuss.elastic.co/u/nick.e)\
**Post date:** [December 13, 2016, 6:27am UTC](https://discuss.elastic.co/t/solved-es-using-ad-authentication-crashes-when-logged-in-through-kibana/68733/3 "2016-12-13T06:27:12Z")

</div>

Nice to hear that you also could solve the problem.

Seems like this is a general problem which should be fixed somehow, because in some cases the **unmapped\_groups\_as\_roles** parameter is useful.  
Or maybe we're just using it wrong, I'm not sure.

---

<div class="post-metadata">

**Author:** ![Terence\_Earl\_Michael](https://avatars.discourse-cdn.com/v4/letter/t/258eb7/32.png) [@Terence\_Earl\_Michael](https://discuss.elastic.co/u/Terence_Earl_Michael)\
**Post date:** [December 13, 2016, 11:14am UTC](https://discuss.elastic.co/t/solved-es-using-ad-authentication-crashes-when-logged-in-through-kibana/68733/4 "2016-12-13T11:14:50Z")

</div>

> [@nick.e](#):
>
> unmapped\_groups\_as\_roles

Hi Nick

I think the difficulty is that the standard advice in the documentation is to set the value to "true" . nonetheless, thank you for solving my issue, everything is working nicely now, although it would be good to assign roles to AD users through the API as opposed to a mapping file...

---

<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:** [January 10, 2017, 11:15am UTC](https://discuss.elastic.co/t/solved-es-using-ad-authentication-crashes-when-logged-in-through-kibana/68733/5 "2017-01-10T11:15:10Z")

</div>

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