#2763 [RFE] sssd: multilevel sub-domain support
Closed: cloned-to-github 3 years ago by pbrezina. Opened 8 years ago by jhrozek.

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

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

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

re-testing shouldn't block 1.14.

milestone: SSSD 1.14 beta => SSSD 1.14 backlog

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)

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

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

4 years 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/3804

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 Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata