Learn more about these different git repos.
Other Git URLs
Some of the backend specific options are needed only when certain condition in program is met (for example SSSD goes offline) and are not checked at startup. This also means that if someone wrongly specifies an option, (for example offline_timeout = 10a0) the problem is discovered by SSSD when the option is first used, which is late. It might be better to check these options during be_ctx initialization, store them to dp_option array and write loud message to logs if something goes wrong.
It is a long standing issue. IMO the validity of the config file should be checked at start and ding-libs should provide a way to check at least the syntax and presence at first. I started some patches in the past I plan to get back to them when I have a chance.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
rhbz: => todo
mark: => 0
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
priority: major => minor sensitive: => 0
Makes sense, but not in 1.15..
milestone: SSSD 1.14 beta => SSSD 1.15 beta
keywords: => easyfix
Metadata Update from @mzidek: - 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/3183
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.