Learn more about these different git repos.
Other Git URLs
Currently responder_get_domain() doesn't check for expired domains but responder_get_domain_by_id() does. We should unify how these helpers and also how their callers should check for return validity.
responder_get_domain()
responder_get_domain_by_id()
Currently it is not a big issue because these getters are only called in situations where we know the subdomains have been just refreshed.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.11 beta rhbz: => 0 type: defect => task
Check. This might have already been fixed.
changelog: => milestone: SSSD 1.13 beta => Interim Bucket priority: minor => major
milestone: Interim Bucket => SSSD 1.12 beta
The ticket #2320 is related and both should be fixed at the same time.
milestone: SSSD 1.12 beta => SSSD 1.13 beta
mark: => 0
Not required in 1.13 proper, moving out to make room for newly arrived tickets.
Pavel, I'll also assign to you, because I'm not sure if this ticket is still valid with the new cache_req code.
milestone: SSSD 1.13 beta => SSSD 1.13 backlog sensitive: => 0
Check if this is still an issue with the cache_req code, if not, close..
milestone: SSSD 1.13 backlog => SSSD 1.14 beta
This will be fixed for free when we move all the responders to the cache_req code.
milestone: SSSD 1.14 beta => SSSD 1.15 beta
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Future releases (no date set yet)
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
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/2944
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.