Skip to content
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

Run LDAP tests against 389-ds #33213

Open
jaymode opened this issue Aug 28, 2018 · 3 comments
Open

Run LDAP tests against 389-ds #33213

jaymode opened this issue Aug 28, 2018 · 3 comments
Labels
help wanted adoptme :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team >test Issues or PRs that are addressing/adding tests

Comments

@jaymode
Copy link
Member

jaymode commented Aug 28, 2018

Currently our LDAP tests are run against an OpenLDAP fixture. A recent announcement shows the RHEL and SLES are withdrawing support for OpenLDAP in favor of 389-ds. This issue is being opened to discuss testing against the 389-ds server in addition to OpenLDAP testing.
@jaymode jaymode added >test Issues or PRs that are addressing/adding tests :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) team-discuss labels Aug 28, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security

@tvernum
Copy link
Contributor

tvernum commented Apr 1, 2019

We discussed this in the ES security meeting some months ago and decided that this made sense, but was a low priority.
For most of our security realms / protocols we only test against a single sample provider (e.g. SAML tests only run against Shibboleth) and given the relatively infrequency of LDAP compatibility issues this is a low priority change (we'd rather add more SAML tests).

@tvernum tvernum added the help wanted adoptme label Apr 1, 2019
@tvernum
Copy link
Contributor

tvernum commented Jul 15, 2019

Given that RHDS / 389DS's member-of plugin claims to automatically expand nested groups
(see also #43921), it might be worth adding it to the test suite so that we are running tests against at least 1 server that has nested group support.

@rjernst rjernst added the Team:Security Meta label for security team label May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted adoptme :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team >test Issues or PRs that are addressing/adding tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rjernst @tvernum @jaymode @elasticmachine