This came up on the upstream devel list:
Right now, we check if the provider is local or not in each data-specific loop. There's one check for users, one check for groups etc. Implementing the local provider as a real provider would have the benefit of keeping the logic same on the responder side regardless of the provider type and also make extending the local provider easier in the future.
milestone: NEEDS_TRIAGE => SSSD 1.11 beta
rhbz: => todo
proposed_priority: => Nice to have
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: SSSD 1.11 beta => SSSD 1.10 beta
priority: major => minor
design_review: => 0
summary: Implement LOCAL provider as a real provider => [RFE] Implement LOCAL provider as a real provider
type: defect => enhancement
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
milestone: SSSD 1.13 beta => SSSD 2.0
review: => 0
moving the ticket to needs_triage for discussion.
mark: => 0
milestone: SSSD 2.0 => NEEDS_TRIAGE
sensitive: => 0
The local provider is not actively developed anymore. When we upstream the work on the files provider, we either deprecate or remove the local provider completely.
In the meantime, I'm moving this ticket into "Patches welcome".
milestone: NEEDS_TRIAGE => SSSD Patches welcome
We will actually remove the local provider.
review: 0 => 1
The files provider was implemented instead.
resolution: => wontfix
status: new => closed
Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Patches welcome
to comment on this ticket.
Copyright © 2014-2017 Red Hat
2.13.2 — Documentation