Skip to content

[Issue]: LDAP Documentation indicates compatibility with Elastic Cloud Hosted deployments #1238

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

Jump to bottom
Closed
mikeisonthenets opened this issue Apr 22, 2025 · 1 comment
Closed

[Issue]: LDAP Documentation indicates compatibility with Elastic Cloud Hosted deployments #1238

mikeisonthenets opened this issue Apr 22, 2025 · 1 comment
Labels
documentation Improvements or additions to documentation source:web Issues originating from the elastic.co docs Team:Platform Issues owned by the Platform Docs Team

Comments

@mikeisonthenets
Copy link

Type of issue

Inaccurate

What documentation page is affected

https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/ldap

What happened?

The documentation page on LDAP authentication contains references and inline notes suggesting LDAP support. However, LDAP is listed as a "known restriction" for Elastic Cloud Hosted in the related documentation.

The current documentation has lead to confusion for users (internal and external) attempting to configure LDAP on Elastic Cloud Hosted, as it implies support where there is none.

This discrepancy should be addressed to prevent misconfiguration and customer frustration when the efforts to edit the ECH Cluster YAML per the docs fails.

Request:

Please review and clarify the documentation to explicitly state the incompatibility of LDAP with Elastic Cloud Hosted.

If possible, provide summary guidance on alternative authentication methods to use instead, such as OpenID Connect or SAML via Azure Active Directory, which are supported and recommended for Elastic Cloud Hosted environments.

Also, a brief explanation of why LDAP is not supported, focusing on security and architectural considerations, would be great.

Additional info

No response
@mikeisonthenets mikeisonthenets added the source:web Issues originating from the elastic.co docs label Apr 22, 2025
@github-actions github-actions bot added the needs-team Issues pending triage by the Docs Team label Apr 22, 2025
@mikeisonthenets mikeisonthenets added the documentation Improvements or additions to documentation label Apr 22, 2025
@KOTungseth KOTungseth added Team:Platform Issues owned by the Platform Docs Team and removed needs-team Issues pending triage by the Docs Team labels Apr 28, 2025
@shainaraskas
Copy link
Collaborator

fixed in #1270

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation source:web Issues originating from the elastic.co docs Team:Platform Issues owned by the Platform Docs Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mikeisonthenets @KOTungseth @shainaraskas