Skip to content

Add known issue for AD and LDAP permissions issue #68875

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jasontedor merged 1 commit into from
Feb 10, 2021
Merged

Add known issue for AD and LDAP permissions issue #68875

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/reference/release-notes/7.11.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,20 @@

Also see <<breaking-changes-7.11,Breaking changes in 7.11>>.

[[known-issues-7.11.0]]
[discrete]
=== Known issues

* Integration with <<active-directory-realm, Active Directory realms>> and
<<ldap-realm, LDAP realms>> is impacted by an issue that prevents
Elasticsearch from starting. If you have configured an Active Directory or
LDAP realm, then Elasticseach will fail to start with an error message
indicating that `Could not initialize class com.unboundid.util.Debug`. This
exception is fatal. If you encounter this during an upgrade, because
Elasticsearch failed during node construction, you can safely downgrade to
your previous version of Elasticsearch. We are actively working on a fix for
this issue. For more details, see {es-issue}68838[#68838].

[discrete]
[[fips-140-2-compliance-7.11.0]]
=== FIPS 140-2 compliance
Expand Down