Whether the PAC responder is enabled or not is tied together with the subdomains support currently.
There might be cases where the user does not want to have the the subdomains provider but he would like to have the PAC responder running. Simo proposed that the PAM responder might have an option to enable the PAC but not the subdomains.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.10 beta rhbz: => todo
selected: => Not need
Moving tickets that are not a priority for SSSD 1.10 into the next release.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
Add an option to PAC responder that PAC responder should not be started. It only makes sense for IPA provider as we do not start it automatically for AD provider.
changelog: => priority: major => minor review: => 0
mark: => 0
It would be better to socket-activate the responders.
milestone: SSSD 1.13 beta => SSSD 1.13 backlog priority: minor => trivial
Mass-moving tickets not planned for any immediate release and re-setting priority.
milestone: SSSD 1.13 backlog => SSSD Deferred priority: trivial => major
Setting "candidate to be pushed out" so that we at least discuss if this ticket makes sense or can be closed.
review: 0 => 1 sensitive: => 0
Since we already have a PR to socket-activate the responders, I'm closing this ticket as invalid.
resolution: => wontfix status: new => closed
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Patches welcome
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/2684
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.