SSSD / sssd

#2393 failover: enable different dns discovery domain for AD subdomains
Closed: wontfix by pbrezina. Opened by pbrezina.

Closed: wontfix
Reopen Issue

Current SRV AD plugin does not allow to set different dns discovery domains for trusted subdomains if dns_discovery_domain is set in sssd.conf. Therefore if the option is present, we always look up directory controllers in the domain configured in dns_discovery_domain. This means that the obtained servers for subdomains are wrong and we are not able to look up users and groups (unless the found dc is also gc).

Fields changed

blocking: => #2394

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta

Fields changed

rhbz: => 0

Fields changed

mark: => 0

This would be nice to have, but requires quite a bit of refactoring of the failover code.

milestone: SSSD 1.13 beta => SSSD 1.13 backlog

Mass-moving tickets not planned for the 1.13 release to 1.14

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

This would be nice to have, but the changes required for the failover and responder refactoring are not scoped for the 1.14 release.

milestone: SSSD 1.14 beta => SSSD 1.15 beta
sensitive: => 0

Metadata Update from @pbrezina:
- Issue marked as blocked by: #2394
- Issue set to the milestone: SSSD Future releases (no date set yet)

Metadata Update from @thalman:
- Custom field blocking reset (from #2394)
- 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

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)

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

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

Candidate to close

None
None
Normal
defect
SSSD
1.12.0
0
false
false
false
false
false
false
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.