-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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.
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
LDAP Search failing during nested group search with "Bad search filter" #9110
Comments
What's also mildly interesting, is that when I change the key values to below, I get the same issues, even to the point where the nested search filter uses ou=people, even though I've deleted ou=people from the LDAP Base DN
|
And I have tried with LDAP Scope and LDAP Group Scope at Base, Subtree, and OneLevel |
Hello, I too have this error when trying to integrate with ldap on free-ipa.
results in (regardless of scope-settings):
harbor Version v1.9.0-d13cf448 |
It seems this issue related to the PR #8378, the nest group filter doesn't work in some LDAP server |
Is this going to be fixed? We are also running into this problem with Free IPA. Is there a workaround? |
Hi, Same bug here with 1.9.0 was working in 1.8.x |
Is there a simple way to downgrade Harbor? It always tries to run the database migration scripts, which don't exist. Perhaps a scary, long CLI flag can be added to aid in these situations. I'm trying not to cry, but this broke production for us. |
It looks like an AD specific search has been added: 51eb8bc#diff-10b1fa8fc186f561edae8dc96ac6cc39 Correct me if I'm wrong, but 1.2.840.113556.1.4.1941 is an AD specific matching rule and there should be no expectation for FreeIPA or 389DS to support it: https://ldapwiki.com/wiki/LDAP_MATCHING_RULE_IN_CHAIN Are there any plans to turn off this search for LDAP servers that aren't AD? |
Same issue here with OpenLDAP:
|
Hello. Same issue here with Oracle DS.
With ldapsearch.
|
I've built an image with the nested group code commented out. If you're brave enough to give it a try, replace the image spec in your docker-compose.yml:
|
It works.
|
@CoaxVex did you submit a PR? |
No, I just disabled the nested group functionality: https://gist.github.com/CoaxVex/68a48d444a9e9256ceab892d57db5feb |
Remove the code change in goharbor#8378, because the previous code change caused issues: goharbor#9092, goharbor#9110, goharbor#9326 Signed-off-by: stonezdj stonezdj@gmail.com
Remove the code change in goharbor#8378, because the previous code change caused issues: goharbor#9092, goharbor#9110, goharbor#9326 Signed-off-by: stonezdj <stonezdj@gmail.com>
Remove the code change in goharbor#8378, because the previous code change caused issues: goharbor#9092, goharbor#9110, goharbor#9326 Signed-off-by: stonezdj <stonezdj@gmail.com>
Remove the code change in goharbor#8378, because the previous code change caused issues: goharbor#9092, goharbor#9110, goharbor#9326 Signed-off-by: stonezdj <stonezdj@gmail.com>
Trying to setup Harbor LDAP authentication, and running into an issue that I'm not sure I understand.
Here's my configuration values:
When my users log in, the logs show this:
Is there another setting we could be using that would make this work? The search appears to work just fine for finding the user, and finding the groups, but not on the final nested groups search. We also don't use nested groups - would that be something we could config to off?
Harbor Version v1.9.0-76f15806
The text was updated successfully, but these errors were encountered: