SSSD / sssd

#2294 In sssd.conf, setting "ldap_group_nesting_level = 0" does not appear to work
Closed: Fixed Opened by jhrozek.

Closed: Fixed
Reopen Issue

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1082633

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
On rhel6.4 configured as AD client using sssd, running
ssd-1.9.2-129.el6_5.4.x86_64 ( with RFC2307bis).  With ldap_group_nesting_level
= 0   should block the nesting operations.  However it seems that sssd is
ignoring the this value set for option.
Version-Release number of selected component (if applicable):
ssd-1.9.2-129.el6_5.4.x86_64
How reproducible:
Always
Steps to Reproduce:
1. in the sssd.conf ,   in the domain section,  define the following parameter
ldap_group_nesting_level = 0
2. restart the sssd service,
3. Create or modify userA  and  Group_A, Group_B, Group_C.
4. Make Group_B  member of Group_A & Group_C member of Group_B
5. With User_A member of Group_C,  the id
Actual results:
With ldap_group_nesting set to "0",   run  '$ id UserA'
and the output will show GroupA, GroupB, GroupC
Expected results:
UserA in GroupC =  Without Nesting should show C only
UserA in GroupB =  Without Nesting should show B only
Additional info:

Here is a preliminary patch written when triaging the case originally:
http://fedorapeople.org/cgit/jhrozek/public_git/sssd.git/log/?h=nesting

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11.6

Fields changed

owner: somebody => jhrozek

Fields changed

owner: jhrozek => preichl
status: new => assigned

Fields changed

patch: 0 => 1

Pushed to master:
- 69994add9cd4e57d40b3b7a0b1783ef2d0aa974c
- c30f1d05d6c75080fbe8ea9868f291e7a331ad44
- 3c1899348804713b49ba9c1f2bc782892c47c2fa
and to sssd-1-11:
- 4221bd76e2b631684f2dc7e8c625fd7b27947cf8
- 98052f6f186f27a6fde4786274132a6bb4d69e79
- e97a7f5bfbb6de33fd722cf613dbaea042126ca6

_comment0: Pushed to master:
69994add9cd4e57d40b3b7a0b1783ef2d0aa974c
c30f1d05d6c75080fbe8ea9868f291e7a331ad44
3c1899348804713b49ba9c1f2bc782892c47c2fa
and to sssd-1-11:
4221bd76e2b631684f2dc7e8c625fd7b27947cf8
98052f6f186f27a6fde4786274132a6bb4d69e79
e97a7f5bfbb6de33fd722cf613dbaea042126ca6
=> 1401729487304105
resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.11.6

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/3336

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.
Metadata
None
None
None
Normal
defect
SSSD
None
0
1
https://bugzilla.redhat.com/show_bug.cgi?id=1082633
0
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.