Learn more about these different git repos.
Other Git URLs
These two options are completely useless, and are contributing to confusion when setting up SSSD. All modern LDAP servers are sufficiently indexed to make it unnecessary to specify user and group bases separately.
Many users are setting up 'ldap_user_search_base' instead of 'ldap_search_base' and are then confused because their groups are not visible.
I object, these are very useful features in some setups, and are available also in nss_ldap. User's will always find ways to mis-configure their systems, removing features is not the way to fix that. If these options are confusing move them into an "Advanced" section in the man page, and clearly explain what should be used by default in their description. This is a documentation issue, really.
I agree with Simo. Making this a documentation issue.
component: LDAP Provider => Documentation doc: 0 => 1 milestone: NEEDS_TRIAGE => SSSD 1.4.0 owner: somebody => davido
Deployment Guide updated. Patch available in next build. Man pages still to do.
Fields changed
summary: Remove ldap_user_search_base and ldap_group_search_base => Properly document ldap_user_search_base and ldap_group_search_base
Who normally addresses man page issues? (I'll give you a hint - not normally me :) )
I can but only if people are aware that this time will be taken out of the IPA schedule, and there's not much of that to go around.
owner: davido => jzeleny
status: new => assigned
Fixed by 3fda983
docupdated: 0 => 1 fixedin: => 1.4.0 resolution: => fixed status: assigned => closed
rhbz: => 0
Metadata Update from @sgallagh: - Issue assigned to jzeleny - Issue set to the milestone: SSSD 1.4.0
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1649
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.