Description of problem:
The sssd-ldap manual page says:
Specify the Kerberos REALM (for SASL/GSSAPI auth).
Default: System defaults, see /etc/krb5.conf
That's not true since we added the online/offline callbacks to create and delete kdcinfo files. They require the realm to be specified to construct the pathname of the kdcinfo files.
If the realm is not specified, the provider does not even start and quits with a rather confusing error message (the code strdups the NULL realm and thinks it hits an OOM situation).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure an LDAP provider with GSSAPI authentication and omit the krb5_realm option
2. start sssd
the provider does not start
the provider should start
Verified in version:
# rpm -qi sssd | head
Name : sssd Relocations: (not relocatable)
Version : 1.5.1 Vendor: Red Hat, Inc.
Release : 52.el6 Build Date: Tue 20 Sep 2011 09:11:03 PM IST
Install Date: Mon 26 Sep 2011 05:56:30 PM IST Build Host: x86-010.build.bos.redhat.com
Group : Applications/System Source RPM: sssd-1.5.1-52.el6.src.rpm
Size : 3550647 License: GPLv3+
Signature : (none)
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL : http://fedorahosted.org/sssd/
Summary : System Security Services Daemon
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Cause: The LDAP provider manual page stated that GSSAPI authentication is used and the Kerberos realm is not specified, the
system default would be used. However, the LDAP provider code did not fall back to the system default Kerberos realm when
the realm was not specified in the config file.
Consequence: The documentation did not match the code
Fix: The LDAP provider was fixed so that it is able to fall back to the default realm configured in /etc/krb5.conf
Result: The documentation matches the code
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.