Learn more about these different git repos.
Other Git URLs
Some responders, such as ssh or sudo don't have to be running all the time, but can be socket activated instead.
We should optionally allow responders to be socket-activated. This would require changes to the monitor code, in particular how we start responders and how we ping them.
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
rhbz: => 0
summary: RFE: Socket-activate responders => [RFE] Socket-activate responders
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1080960 (Red Hat Enterprise Linux 7)
rhbz: 0 => [https://bugzilla.redhat.com/show_bug.cgi?id=1080960 1080960]
Please also check out #2292 when working on this ticket.
mark: => 1
Makes sense for the local backend
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
Required for the secrets-as-a-service work.
sensitive: => 0
owner: somebody => simo
patch: 0 => 1
On second thougt, I created (and closed) ticket #3070. I think it would be better to keep this ticket open until all the tooling and documentation is in place and responders are started with systemd in upstream by default on platforms that support it.
milestone: SSSD 1.14 beta => SSSD 1.16 beta
patch: 1 => 0
design: => https://fedorahosted.org/sssd/wiki/DesignDocs/SocketActivatableResponders
design_review: 0 => 1
owner: simo => fidencio
Patch set is part of pull-request 94 (https://github.com/SSSD/sssd/pull/94)
_comment0: Patches are part of the PR#84:
https://github.com/SSSD/sssd/pull/84 => 1480031796323833
patch: 0 => 1
milestone: SSSD Future releases (no date set yet) => SSSD 1.15 Alpha
resolution: => fixed
status: new => closed
Metadata Update from @jhrozek:
- Issue assigned to fidencio
- Issue marked as blocked by: #3245
- Issue set to the milestone: SSSD 1.15.0
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:
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.
to comment on this ticket.