Bug #12167
closed
LDAP Group sync fails with UIDNotFoundException
Added by Timo Goebel about 9 years ago.
Updated about 9 years ago.
Description
I experience an issue with ldap group sync in 1.9.2. Foreman raises an 500 exception with "LdapFluff::ActiveDirectory::MemberService::UIDNotFoundException".
This happens when adding, refreshing or deleting the group.
I tested with a single group. That group contains only valid users. They are not all known to foreman, though. (as they have not logged in before)
I checked the base dns. All users in the group can possibly be found.
I tested with active directory.
Trace:
http://pastie.org/private/hwh9s12plur2bz9fsqytg
- Status changed from New to Need more information
Does the user's CN contain any commas? If so, that's just been fixed (https://github.com/theforeman/ldap_fluff/pull/46).
Otherwise, it would be useful if you could paste the ldapsearch output of your group and users, and also the values of both the base DN and group base DN in the LDAP configuration in Foreman.
Yes, this was related to commas in the DN. Works with the patch applied. Thanks.
- Is duplicate of Bug #8840: LDAP Usergroup Refresh fails when User CN contains escaped characters added
- Status changed from Need more information to Duplicate
Thanks for testing it! I'll try and make sure it gets released shortly, probably for a 1.10.0 RC or .1.
Also available in: Atom
PDF