This ticket tracks the discussion about enabling socket-activate services to refresh configuration https://firstname.lastname@example.org/message/WB6OHNWYFJ5QSCKV6RA7UAEUHA3IZ5KY/
The problem definition is that while the socket-activated responders (kcm,secrets) can be activated without sssd running, any configuration changes of these responders require restart of SSSD, which might be non-obvious and even problematic as the user might not need SSSD to serve any domains at all.
Is this ticket about short term solution (just for kcm, secrets) or about long term solution (everything socket activated)? Because the discussion/meeting was mostly about long term solution.
Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.4
to comment on this ticket.
Copyright © 2014-2017 Red Hat
2.90.1 — Documentation