Bug 771951

Summary:	fall back to defaults from krb5.conf if the realm is not specified explicitly in sssd.conf
Product:	Red Hat Enterprise Linux 7	Reporter:	Dmitri Pal <dpal>
Component:	sssd	Assignee:	SSSD Maintainers <sssd-maint>
Status:	CLOSED DEFERRED	QA Contact:	Kaushik Banerjee <kbanerje>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	grajaiya, jhrozek, mkosek, prc, rmainz
Target Milestone:	pre-dev-freeze
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-24 11:21:40 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-01-05 14:11:23 UTC

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

In most cases, like kerberos and IPA provider, SSSD enforces that the realm must be specified in the config file. On the other hand, in the case of using LDAP provider with GSSAPI mech, the realm is not required and the ldap_child can autodiscover it from /etc/krb5.conf.

I think it would be better if the behaviour was the same in all providers. Simo even suggested that we might make the krb5_realm option optional and fall back to getting the realm via krb5_get_default_realm.

Comment 3 Jakub Hrozek 2014-07-02 15:04:43 UTC

The upstream ticket is targetting 1.13, so I'm reproposing the BZ to RHEL-7.2

Comment 4 Martin Kosek 2015-04-24 11:21:40 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.