#1925 [RFE] Build a generic mechanism to invoke a callback after a provider is reconfigured
Closed: wontfix 4 years ago by pbrezina. Opened 10 years ago by jhrozek.

The SSSD could benefit from a generic mechanism to invoke a per-provider callback after a configuration has been changed. Examples of what could be handled are invoking a DNS update after the hostname has changed or GPO policy pull.

See rhbz #867864 for more details.

Stef Walter came with this nice idea.


The ini parser has now a capability to compare the config objects. The idea is to detect that the configuration has changed. SSSD would have to implement either an inotify watch or check the config file periodically or trigger config check as a result of a particular signal SIGHUP for example.
This however would require a bit of refactoring of the INI handing code because current logic is to dump everything into the DB first. Instead SSSD should interact with the in memory configuration stored in config object and use the DB only as a persistent backup. I would argue that may be the system DB can actually be removed because it does not add a value over the file.

look for ini_config_changed function in https://git.fedorahosted.org/cgit/ding-libs.git/tree/ini/ini_parse_ut.c for the example code on how to detect that config has changed.
A more elaborate check can be added if needed.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta
summary: RFE: Build a generic mechanism to invoke a callback after a provider is reconfigured => [RFE] Build a generic mechanism to invoke a callback after a provider is reconfigured
type: defect => enhancement

Fields changed

rhbz: => 0

This ticket makes sense, but the 1.14 milestone is already too big. I'm moving the ticket to 1.15 beta

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

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: Canditate to close

4 years ago

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)

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

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.

Login to comment on this ticket.

Metadata