# Be Careful With 7.11.0 Update If You Use LDAP With Realms

**URL:** <https://discuss.elastic.co/t/be-careful-with-7-11-0-update-if-you-use-ldap-with-realms/264253>\
**Category:** Elasticsearch\
**Created:** [February 14, 2021, 4:45pm UTC](https://discuss.elastic.co/t/be-careful-with-7-11-0-update-if-you-use-ldap-with-realms/264253 "2021-02-14T16:45:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![patrickmm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrickmm/32/39009_2.png) [@patrickmm](https://discuss.elastic.co/u/patrickmm)\
**Post date:** [February 14, 2021, 4:45pm UTC](https://discuss.elastic.co/t/be-careful-with-7-11-0-update-if-you-use-ldap-with-realms/264253/1 "2021-02-14T16:45:22Z")

</div>

About an hour ago, I tried updating my on prem 7.10.2 dev cluster (RHEL 8, 15 nodes) to 7.11.0.

On the first node I ran yum update on, when I restarted Elasticsearch, it failed. I looked at journalctl and saw errors related to LDAP. Doing some searching led me to the following discussion on Elastic's GitHub: [Fix permissions for UnboundID LDAP SDK by jasontedor · Pull Request #68872 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/pull/68872) .

I wanted to surface this issue for anyone else in the community who uses LDAP with realms for authentication and is considering an upgrade to 7.11.0. It looks like we need to wait for 7.11.1.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 14, 2021, 5:07pm UTC](https://discuss.elastic.co/t/be-careful-with-7-11-0-update-if-you-use-ldap-with-realms/264253/2 "2021-02-14T17:07:13Z")

</div>

Very true sadly.

The [download page](https://www.elastic.co/downloads/elasticsearch) says:

> We have identified a bug that will affect deployments on ECE, ECK, or any stand-alone deployment with LDAP or Active Directory configured.
> 
> Deployments with an LDAP or Active Directory realm for authentication configured and upgraded to 7.11.0, in addition to new 7.11.0 deployments in which you configure an LDAP, or Active Directory realm will see all nodes fail to start. If when starting Elasticsearch you see an error message containing "Could not initialize class com.unboundid.util.Debug" then you are impacted by issue.
> 
> As mentioned, we have identified the issue, committed the fix, and are currently working on getting the next version released. In the meantime, do not upgrade to 7.11.0 if you have LDAP or Active Directory configured in your deployment.

---

<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 14, 2021, 5:08pm UTC](https://discuss.elastic.co/t/be-careful-with-7-11-0-update-if-you-use-ldap-with-realms/264253/3 "2021-03-14T17:08:07Z")

</div>

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