Learn more about these different git repos.
Other Git URLs
The SSSD is written under the assumption that any server supporting 2307bis has memberOf attribute. This is not the case with eDirectory and the assumption that any 2307bis compliant server would have memberOf attribute in user entry does not hold.
For more details see: https://www.redhat.com/archives/freeipa-users/2010-July/msg00036.html
Fields changed
component: SSSD => LDAP Provider
description: The SSSD is written under the assumption that any server supporting 2307bis has memberOf attribute. This is not the case with eDirectory and the assumption that any 2307bit compliant server would have memberOf attribute in user entry does not hold.
For more details see: https://www.redhat.com/archives/freeipa-users/2010-July/msg00036.html => The SSSD is written under the assumption that any server supporting 2307bis has memberOf attribute. This is not the case with eDirectory and the assumption that any 2307bis compliant server would have memberOf attribute in user entry does not hold.
For more details see: https://www.redhat.com/archives/freeipa-users/2010-July/msg00036.html milestone: NEEDS_TRIAGE => SSSD 1.4.0 summary: Support eDirectory as a back server for SSSD => SSSD does not properly lookup groups for 2307bis
milestone: SSSD 1.4.0 => SSSD 1.5.0 owner: somebody => sgallagh
priority: major => critical
milestone: SSSD 1.5.0 => SSSD 1.2.4
Fixed by: - 8971b82 - 7272e6f
fixedin: => 1.2.4 resolution: => fixed status: new => closed
rhbz: => 0
Metadata Update from @dpal: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 1.2.4
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/1637
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.