[RFE] sssd: multilevel sub-domain support

[sssd-bot]

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

• Created at 2015-08-19 10:05:18 by jhrozek
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1254697
  • https://bugzilla.redhat.com/show_bug.cgi?id=1343768

---

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1254697

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

1. Proposed title of this feature request
  [RFE] sssd: multilevel sub-domain support

3. What is the nature and description of the request?
  Add support to sssd to support more than one level of sub-domain. At this
time sssd only supports one level of sub-domain.

4. Why does the customer need this? (List the business requirements here)
  winbind supports this and would like sssd to have same functionality.

5. How would the customer like to achieve this? (List the functional
requirements here)
  Add functionality similar to ldap_group_nesting_level to control how many
levels to check.

subdomain_level = 3

6. For each functional requirement listed, specify how Red Hat and the customer
can test to confirm the requirement is successfully implemented.

  Setup with transitive trust:

  example.com
       |_ na.example.com
              |_ us.na.example.com

  Setup sssd to example.com using option "subdomain_level = 3"

  # getent passwd <aduser>@us.na.example.com

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
  N/A

Comments

---

Comment from jhrozek at 2015-08-20 17:05:07

Filing into 1.14 so the ticket gets discussed along with other 1.14 tickets although I stronly suspect it's out of scope for 1.14...

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
milestone: NEEDS_TRIAGE => SSSD 1.14 beta
review: True => 0
selected: =>
testsupdated: => 0

---

Comment from jhrozek at 2016-02-16 14:03:25

This should already work, but we need to re-test this functionality

---

Comment from jhrozek at 2016-06-20 11:44:21

re-testing shouldn't block 1.14.

milestone: SSSD 1.14 beta => SSSD 1.14 backlog

---

Comment from jhrozek at 2016-11-28 11:44:35

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1343768 (Red Hat Enterprise Linux 7)

rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=1254697 1254697] => [https://bugzilla.redhat.com/show_bug.cgi?id=1254697 1254697], [https://bugzilla.redhat.com/show_bug.cgi?id=1343768 1343768]

---

Comment from jhrozek at 2016-12-15 11:01:09

Since the 1.14 branch is transitioning into maintenance mode and new functionality is being developed in master which will become 1.15 eventually, I'm mass-moving tickets from the 1.14 backlog milestone to the "Future releases" milestone.

milestone: SSSD 1.14 backlog => SSSD Future releases (no date set yet)

---

Comment from jhrozek at 2017-02-24 14:51:16

Metadata Update from @jhrozek:

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

---

Comment from thalman at 2020-03-13 12:07:17

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: bugzilla

[andreboscatto]

Dear Contributor/User,

Recognizing the importance of addressing enhancements, bugs, and issues for the SSSD project's quality and reliability, we also need to consider our long-term goals and resource constraints.

After thoughtful consideration, regrettably, we are unable to address this request at this time. To avoid any misconception, we're closing it; however, we encourage continued collaboration and contributions from anyone interested.

We apologize for any inconvenience and appreciate your understanding of our resource limitations. While you're welcome to open a new issue (or reopen this one), immediate attention may not be guaranteed due to competing priorities.

Thank you once again for sharing your feedback. We look forward to ongoing collaboration to deliver the best possible solutions, supporting in any way we can.

Best regards,
André Boscatto

CC: @tscherf