# Ldap user unable to login after upgrade to 6.6.1

**URL:** https://discuss.elastic.co/t/ldap-user-unable-to-login-after-upgrade-to-6-6-1/170980
**Category:** Kibana
**Created:** [March 5, 2019, 7:26pm UTC](https://discuss.elastic.co/t/ldap-user-unable-to-login-after-upgrade-to-6-6-1/170980 "2019-03-05T19:26:12Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Kevin\_Comer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kevin_comer/32/42550_2.png) [@Kevin\_Comer](https://discuss.elastic.co/u/Kevin_Comer)
#### Post date: [March 5, 2019, 7:26pm UTC](https://discuss.elastic.co/t/ldap-user-unable-to-login-after-upgrade-to-6-6-1/170980/1 "2019-03-05T19:26:12Z")

</div>

I just upgraded a test cluster and now I'm not able to login as a user which is in an ldap group for superusers.  
I'm getting the error below  
Error in Browser  
{"message":"action [indices:data/read/search] is unauthorized for user [user123]: [security\_exception] action [indices:data/read/search] is unauthorized for user [user123]","statusCode":403,"error":"Forbidden"}

I have added a superuser role\_mapping in the Elastic API as well as in the /etc/elasticsearch/role\_mapping.yml file

API  
"superuser" : {  
"enabled" : true,  
"roles" : [  
"superuser"  
],  
"rules" : {  
"field" : {  
"groups" : "CN=sdlc\_elasticsearch\_admin,OU=elk,OU=appgroups,OU=accessmgmnt,DC=something,DC=something,DC=com"  
}  
},  
"metadata" : { }  
}  
}

Any Ideas how I may resolve this issue?

---

<div class="post-metadata">

### Author: ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)
#### Post date: [March 5, 2019, 9:24pm UTC](https://discuss.elastic.co/t/ldap-user-unable-to-login-after-upgrade-to-6-6-1/170980/2 "2019-03-05T21:24:09Z")

</div>

Hey @Kevin_Comer, which version were you on prior to the upgrade?

---

<div class="post-metadata">

### Author: ![Kevin\_Comer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kevin_comer/32/42550_2.png) [@Kevin\_Comer](https://discuss.elastic.co/u/Kevin_Comer)
#### Post date: [March 5, 2019, 9:38pm UTC](https://discuss.elastic.co/t/ldap-user-unable-to-login-after-upgrade-to-6-6-1/170980/3 "2019-03-05T21:38:08Z")

</div>

6.3.2

---

<div class="post-metadata">

### Author: ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)
#### Post date: [March 5, 2019, 9:55pm UTC](https://discuss.elastic.co/t/ldap-user-unable-to-login-after-upgrade-to-6-6-1/170980/4 "2019-03-05T21:55:58Z")

</div>

Are you seeing that error message directly after logging in to Kibana?

---

<div class="post-metadata">

### Author: ![Kevin\_Comer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kevin_comer/32/42550_2.png) [@Kevin\_Comer](https://discuss.elastic.co/u/Kevin_Comer)
#### Post date: [March 5, 2019, 10:20pm UTC](https://discuss.elastic.co/t/ldap-user-unable-to-login-after-upgrade-to-6-6-1/170980/5 "2019-03-05T22:20:36Z")

</div>

Yes I was getting this directory in the browser after logging and I was just now able to resolve this with a change in my ldap configuration.

My group search base dn changed and this test cluster did not get updated. I corrected this and now Im able to login.

Thank You

---

<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: [April 2, 2019, 10:20pm UTC](https://discuss.elastic.co/t/ldap-user-unable-to-login-after-upgrade-to-6-6-1/170980/6 "2019-04-02T22:20:40Z")

</div>

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