#3425 ldap_group_nesting_level 0 still leads to searches for parent groups of groups with rfc2307bis schema
Closed: wontfix 2 months ago by pbrezina. Opened 2 years ago by jstephen.

In the case of using LDAP provider with rfc2307bis schema and ldap_group_nesting_level = 0 SSSD still performs nested group searches(parent groups of group searches):

[rfc2307bis_nested_groups_send] (0x2000): About to process 43 groups in nesting level 0
[sdap_get_primary_name] (0x0400): Processing object testgroup
[rfc2307bis_nested_groups_step] (0x1000): Processing group [testgroup@example.com]
[rfc2307bis_nested_groups_next_base] (0x0400): Searching for parent groups of group [CN=testgroup,OU=Groups,DC=EXAMPLE,DC=COM] with base [OU=Groups,DC=example,DC=com]

Metadata Update from @jstephen:
- Issue assigned to jstephen

2 years ago

Metadata Update from @jstephen:
- Custom field rhbz adjusted to 1459660

2 years ago

Metadata Update from @jstephen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1459660 (was: 1459660)

2 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.3

2 years ago

Metadata Update from @jhrozek:
- Issue priority set to: major

2 years ago

There is already a PR, but it is being reviewed and upstream needs to release the next version quite soon. Therefore I'm moving this ticket to the next version.

For the immediate future, triaging tickets with patches is our priority so that you don't wait for including your contribution for even longer.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)

2 years ago

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.4)
- Issue status updated to: Closed (was: Open)

2 years ago

Metadata Update from @lslebodn:
- Issue status updated to: Open (was: Closed)

2 years ago

Ticket is reopened because:

It broke a test for enumerate nested groups if they are part
of non POSIX groups https://pagure.io/SSSD/sssd/issue/2406

Metadata Update from @lslebodn:
- Issue tagged with: regression

2 years ago

Metadata Update from @lslebodn:
- Issue untagged with: regression
- Issue priority set to: blocker (was: major)

2 years ago

Since we are trying to release a new upstream tarball for several days (if not weeks now) and the simplest way forward is to temporarily revert the fix for this ticket and fix it again in the next upstream release (1.15.4), I'm moving this ticket to 1.15.4.

The original fix was reverted as of 9349370

FWIW (because the revert PR might not be trivial to find) the test that uncovered the regression was downstream (RH-specific) test for upstream https://pagure.io/SSSD/sssd/issue/2406

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)

2 years ago

Metadata Update from @jhrozek:
- Issue tagged with: cleanup-one-sixteen

2 years ago

Metadata Update from @jhrozek:
- Issue untagged with: cleanup-one-sixteen
- Issue priority set to: major (was: blocker)
- Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15.4)

2 years ago

Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)

2 years ago

Metadata Update from @jhrozek:
- Issue tagged with: bug, postpone-to-2-0

2 years ago

Metadata Update from @jhrozek:
- Issue untagged with: postpone-to-2-0
- Issue set to the milestone: SSSD 2.0 (was: SSSD 1.16.1)

2 years ago

Metadata Update from @jhrozek:
- Issue priority set to: minor (was: major)

2 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)

2 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

a year ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)

a year ago

Metadata Update from @thalman:
- Issue tagged with: Canditate to close, bugzilla

2 months ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

2 months ago

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

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.

Login to comment on this ticket.

Metadata