Learn more about these different git repos.
Other Git URLs
https://bugzilla.redhat.com/show_bug.cgi?id=820585 (Red Hat Enterprise Linux 6)
Description of problem: Group enumeration fails in proxy provider Version-Release number of selected component (if applicable): 1.8.0-25 How reproducible: Always Steps to Reproduce: 1. Configure nss_ldap and verify if enumeration works via nss_ldap: # getent -s ldap group Group1:*:1001:puser1 Group2:*:1002: Group3:*:999: Group4:*:1011: Duplicate:*:1010: # getent -s ldap passwd puser1:*:1001:1001:Posix User1:/home/puser1:/bin/bash puser2:*:1002:1002:Posix User2:/home/puser2:/bin/bash puser3:*:999:999:Posix User1:/home/puser3:/bin/bash puser4:*:1011:1011:Posix User4:/home/puser4: 2. Configure sssd via proxy: [domain/PROXY] id_provider = proxy auth_provider = proxy debug_level = 0xFFF0 proxy_lib_name = ldap proxy_pam_target = sssdproxyldap enumerate = true 3. Check if enumeration works via sssd: # getent -s sss passwd puser1:*:1001:1001:Posix User1:/home/puser1:/bin/bash puser2:*:1002:1002:Posix User2:/home/puser2:/bin/bash puser3:*:999:999:Posix User1:/home/puser3:/bin/bash puser4:*:1011:1011:Posix User4:/home/puser4: # getent -s sss group <== Nothing is returned Actual results: Group enumeration fails. Expected results: Group enumeration should succeed. Additional info:
Fields changed
blockedby: => blocking: => coverity: => feature_milestone: => owner: somebody => jhrozek patch: 0 => 1 status: new => assigned tests: => 0 testsupdated: => 0 upgrade: => 0
milestone: NEEDS_TRIAGE => SSSD 1.8.4 (LTM)
priority: major => blocker version: => 1.8.3
Fixed by: - 85e82e6 (master) - c8bc8dd (sssd-1-8)
resolution: => fixed status: assigned => closed
Metadata Update from @jhrozek: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.8.4 (LTM)
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/2371
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.