RFE : enable SSSD to support range retrieval even when the search filters are being used

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/2876

• Created at 2015-11-19 17:08:09 by jhrozek
• Closed at 2020-03-24 14:05:59 as wontfix
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1282686

---

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

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

Some users prefer to limit the search bases they use with a filter and disable dereference (because dereference is all-or-nothing). This doesn't work with range retrievals, though, because range retrieval depends on dereference.

However, range retrieval is an AD specific feature and ASQ (AD's dereference method) seems to support filters. Maybe we could modify the range retrieval code to use the provided filter along with ASQ.

Comments

---

Comment from jhrozek at 2015-11-25 15:37:32

The downstream report is no longer urgent, 1.15 is fine.

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

---

Comment from jhrozek at 2015-11-25 15:38:12

In reality this might happen even later, but I don't want to defer the ticket completely.

---

Comment from jhrozek at 2015-11-26 17:03:06

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.15 beta

---

Comment from jhrozek at 2017-02-24 14:35:04

Metadata Update from @jhrozek:

• Issue set to the milestone: SSSD Future releases (no date set yet)

---

Comment from thalman at 2020-03-13 12:00:29

Metadata Update from @thalman:

• Custom field design_review reset (from 0)
• Custom field mark reset (from 0)
• Custom field patch reset (from 0)
• Custom field review reset (from 0)
• Custom field sensitive reset (from 0)
• Custom field testsupdated reset (from 0)
• Issue close_status updated to: None
• Issue tagged with: Canditate to close, bugzilla

---

Comment from pbrezina at 2020-03-24 14:05:58

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.

---

Comment from pbrezina at 2020-03-24 14:06:00

Metadata Update from @pbrezina:

• Issue close_status updated to: wontfix
• Issue status updated to: Closed (was: Open)