#1308 [RFE] Add "provider=..." option to simplify SSSD configuration
Closed: Invalid None Opened 12 years ago by jzeleny.

Each backend can have multiple providers. In many cases IPA backend is the only one that provides some specific functionality (subdomains, session, hostid, ...). These have to be usually explicitly configured in sssd.conf because default value is usually "none".

After a consultation with Jakub, we agreed that IPA backend should be more self configurable, i.e. only setting {{{id_provider = ipa}}} should be enough and all other providers should be set to the same value.

For this to be possible the best approach is to define init functions for all providers in each backend and not give the name of ID provider as default value to load_backend_module().


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11 beta

Fields changed

summary: Make changes in backend so the IPA provider is more self-configurable => [RFE] Make changes in backend so the IPA provider is more self-configurable
type: task => enhancement

The approach here should be to implement new option:

{{{provider = ...}}}

When using this option, all other providers (id, auth, ...) should default to the value used in this option. Also the requirement is that any provider can be either set to different value or disabled by setting it to {{{none}}}.

Fields changed

summary: [RFE] Make changes in backend so the IPA provider is more self-configurable => [RFE] Add "provider=..." option to simplify SSSD configuration

Fields changed

proposed_priority: => Optional

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.

Fields changed

milestone: SSSD 1.11 beta => SSSD 1.12 beta

The downstream ticket was closed and I would like to close this ticket as well. Moving to triage for proper discussion with other developers.

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
mark: => 0
milestone: SSSD 1.14 beta => NEEDS_TRIAGE
review: => 0
selected: =>
sensitive: => 0

We don't plan on implementing this ticket, closing.

resolution: => wontfix
status: new => closed

Metadata Update from @jzeleny:
- Issue set to the milestone: NEEDS_TRIAGE

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

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