#487 Local ID provider should support auth, access and chpass providers
Closed: Invalid None Opened 13 years ago by sgallagh.

Currently, the local provider is deeply built-in to the code. This means that if using the local ID provider, it's not possible to use any other auth, access or chpass provider.

At some point, we will need to be able to support other forms of providers (for example, fingerprint readers, access-control providers, etc.)


Fields changed

component: SSSD => Local Provider

Fields changed

milestone: NEEDS_TRIAGE => SSSD 2.0

Fields changed

rhbz: => 0

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
patch: => 0
proposed_priority: => Optional
upgrade: => 0

This ticket has been evaluated for inclusion into SSSD 1.10 release and was decided to be excluded since it does not match the main goals and themes of the release. It might be considered for later releases.

This will be probably superseded by the "files" provider, nonetheless, I'm moving the ticket to needs_triage for discussion.

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
mark: => 0
milestone: SSSD 2.0 => NEEDS_TRIAGE
review: => 0
selected: =>
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

Fields changed

review: 0 => 1

Since the local provider is not being developed anymore, I'm closing this ticket as wontfix.

resolution: => wontfix
status: new => closed

Metadata Update from @sgallagh:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

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/1529

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.

Login to comment on this ticket.

Metadata