Learn more about these different git repos.
Other Git URLs
This ticket tracks the discussion about enabling socket-activate services to refresh configuration https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahosted.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
Metadata Update from @jhrozek: - Issue tagged with: cleanup-two-point-oh
Metadata Update from @jhrozek: - Issue untagged with: cleanup-two-point-oh - Issue set to the milestone: SSSD 2.0 (was: SSSD 1.15.4)
Metadata Update from @jhrozek: - Issue priority set to: blocker
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)
Duplicate of https://pagure.io/SSSD/sssd/issue/3138
Metadata Update from @thalman: - Custom field design_review adjusted to on - Custom field mark adjusted to on - Custom field patch adjusted to on - Custom field review adjusted to on - Custom field sensitive adjusted to on - Custom field testsupdated adjusted to on - Issue close_status updated to: duplicate - 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/4382
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.