-
Notifications
You must be signed in to change notification settings - Fork 210
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
CS12 LDAP Cannot Handle Duplicated "uid:" field For the Username #71
Comments
Great rundown of the issue from the Samba project: https://bugzilla.samba.org/show_bug.cgi?id=6157 TL:DR We should pick the first "uid:" attribute found in the user record, because that's what nss_ldap would do. For compatibility with Manage, we would need to choose the one that is only letters, numbers, underscores. |
What's the failure we're seeing? If there are duplicate fields in a |
My hunch is that eldap is handing us back something like:
which works great with https://github.com/chef/oc_erchef/blob/95d80e2af0b143e66c111584ed4626db8cfa6663/apps/oc_chef_wm/src/oc_chef_wm_authn_ldap.erl#L156 But when we have multiple Uid fields, if eldap_search is handing us back:
Then that match will fail:
|
It is not uncommone for an LDAP record to have multiple copies of a field, allowing users to be found more easily during search and to account for name changes through time. This change accounts for multiple copies of the LoginAttr field by simply taking the first one that matches the username we were given. Closes chef/chef-server#71
As a customer, I would like Chef Server 12 to handle duplicated fields in user records, like two uid: fields as in
CS12 seems to be tripping up on the above arrangement here
https://github.com/opscode/oc_erchef/blob/95d80e2af0b143e66c111584ed4626db8cfa6663/apps/oc_chef_wm/src/oc_chef_wm_authn_ldap.erl#L155-L159
redbug debugging results and full user record can be found in ZenDesk 2555
redbug results for
find_and_authenticate
for the above data wereThis bug has lower priority than #68
The text was updated successfully, but these errors were encountered: