Bug 814252

Summary:	Add "provider=..." option to simplify SSSD configuration
Product:	Red Hat Enterprise Linux 7	Reporter:	Dmitri Pal <dpal>
Component:	sssd	Assignee:	SSSD Maintainers <sssd-maint>
Status:	CLOSED DEFERRED	QA Contact:	Namita Soman <nsoman>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	jhrozek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-18 20:51:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dmitri Pal 2012-04-19 13:13:00 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/1308

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().

Comment 4 Jakub Hrozek 2016-01-18 20:51:28 UTC

Thank you taking your time and submitting this request for Red Hat Enterprise
Linux. Unfortunately, this bug was not given a priority and was deferred both
in the upstream project and in Red Hat Enterprise Linux.

Given that we are unable to fulfill this request in following Red Hat
Enterprise Linux releases, I am closing the Bugzilla as DEFERRED. To request
that Red Hat re-considers the decision, please re-open the Bugzilla via
appropriate support channels and provide additional business and/or technical
details about its importance to you.

Note that you can still track this request or even contribute patches in the
referred upstream Trac ticket.