Learn more about these different git repos.
Other Git URLs
Calling "id <username>" on an system with empty sssd cached does not give the users secondary groups back. During that call though, the groups will be correctly added to the cache and subsequent "id <username>" invocations will return the correct results.
Note I was using the rfc2307bis schema here and the users's "memberof" attribute is correctly populated.
From the log of the first "id" call:
(Fri Sep 10 16:34:25 2010) [sssd[be[LDAP]]] [sdap_save_groups] (9): Group 4 members processed! (Fri Sep 10 16:34:25 2010) [sssd[be[LDAP]]] [ldb] (9): commit ldb transaction (nesting: 0) (Fri Sep 10 16:34:25 2010) [sssd[be[LDAP]]] [sdap_get_initgr_done] (9): Initgroups done (Fri Sep 10 16:34:25 2010) [sssd[be[LDAP]]] [sdap_id_op_done] (9): releasing operation connection (Fri Sep 10 16:34:25 2010) [sssd[be[LDAP]]] [acctinfo_callback] (4): Request processed. Returned 3,0,Init Groups Failed
Find the rest of the logs attached.
LDAP provider logs sssd_LDAP.log
nss logs sssd_nss.log
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.2.4
owner: somebody => jhrozek
As of today, the issue is only fixed in the 1.2 branch, so I'm leaving the ticket assigned until we forward port the patches to master.
- RFC2307bis case was fixed by the following commits: - 8971b82a5acba9baf85230dbd13b07373904dca1 - 7272e6f982e966454ff8f53f6a261ee9f50bffd8 - RFC2307 case was fixed by commit - ee0b08aaf6a5324149d264e248a6d4ce89aa6c2a
status: new => assigned
I'm closing this ticket. The porting to the master branch is now being tracked in ticket #645.
fixedin: => 1.2.4 resolution: => fixed status: assigned => closed tests: 0 => 1
rhbz: => 0
Metadata Update from @ralf: - Issue assigned to jhrozek - 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/1663
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.