Bug 1075141 – [GSS 7.0] if access_provider is not set sssd fails with no good error

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1075141 - [GSS 7.0] if access_provider is not set sssd fails with no good error

Summary:	[GSS 7.0] if access_provider is not set sssd fails with no good error

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	sssd (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Jakub Hrozek
QA Contact:	Kaushik Banerjee
Docs Contact:

URL:	http//
Whiteboard:
Keywords:

Depends On:
Blocks:	1113520 1064025
	Show dependency tree / graph

Reported:	2014-03-11 10:53 EDT by Dave Sullivan
Modified:	2015-03-05 05:27 EST (History)
CC List:	8 users (show)

See Also:
Fixed In Version:	sssd-1.12.0-1.el7
Doc Type:	Bug Fix
Doc Text:	Cause: The man pages didn't sufficiently explain that when mixing several different types of providers (such as AD provider and LDAP provider), each provider must be fully configured Consequence: As a consequence, users were configuring a mix of providers (typically id_provider=ad and access_provider=ldap) without configuring the LDAP provider fully. Fix: The documentation was amended, stating that the LDAP provider requires separate configuration and is not able to read configuration of the AD provider. Result: Better documentation, less confused admins.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-03-05 05:27:33 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2015:0441	normal	SHIPPED_LIVE	sssd bug fix and enhancement update	2015-03-05 10:05:27 EST

Groups: None (edit)

Description Dave Sullivan 2014-03-11 10:53:49 EDT

Description of problem:

Apparently its critical that "id_provider" and "access_provider" be "ad".  If access_provider is ldap, sssd falls over hard without any good error.  If both are set to "ad", things seem to work correctly and Sites is consulted.


Version-Release number of selected component (if applicable):


How reproducible:

Configure sssd to talk to AD server.

Set id_provider=ad but leave access_provider set to something else.


Actual results:

sssd falls over hard without a good error message


Expected results:

Have sssd indicate via error message that there are inconsistencies with 

"id_provider" and "access_provider"


Additional info:

https://fedorahosted.org/sssd/wiki/Configuring_sssd_with_ad_server 
http://jhrozek.livejournal.com/#post-jhrozek-2801 
http://jhrozek.livejournal.com/#post-jhrozek-3019

Comment 1 Dave Sullivan 2014-03-11 10:56:39 EDT

>>> BZ to look for inconsistencies between access_provider and id_provider
>> OK, but I'd like to ask you to formulate exactly what you see
>> as lacking. I'm all for fixing the documentation, but since I know
>> the internals, the inconsistencies might not be apparent to me.
> I think the BZ here is that sssd doesn't show a good error message
> when this the two above are not in sync or correct.

Makes sense. As a matter of fact, we discovered another similar case
last week, where a user wasn't able to troubleshoot a configuration that
included id_provider=ad && sudo_provider=ldap

Comment 6 Dmitri Pal 2014-03-13 08:57:13 EDT

Upstream ticket:
https://fedorahosted.org/sssd/ticket/2281

Comment 7 Jakub Hrozek 2014-07-14 09:18:39 EDT

Fixed upstream:
    master: b3f56d9e4bd065590383eb1f812a3b77e3c56f24

Comment 9 Kaushik Banerjee 2015-01-06 10:06:55 EST

Verified in version sssd-1.12.2-39.el7

man sssd-ad now includes:

However, unless the “ad” access control provider is explicitly
configured, the default access provider is “permit”. Please note that
if you configure an access provider other than “ad”, you need to set
all the connection parameters (such as LDAP URIs and encryption
details) manually.

Comment 11 errata-xmlrpc 2015-03-05 05:27:33 EST

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0441.html

Note You need to log in before you can comment on or make changes to this bug.