Hide Forgot
Description of problem: SSSD installs an example configuration into /etc/sssd/sssd.conf by default. However, the configuration file contains directives that are not accurate or too low-level. This results in users using non-optimal configurations and getting confused. Version-Release number of selected component (if applicable): sssd-1.5.1-52 How reproducible: always Steps to Reproduce: 1. yum -y install sssd 2. cat /etc/sssd/sssd.conf Actual results: A cluttered example config file. Expected results: A minimal config file with accurate options. Additional info: A prime example is the commented-out local domain with explicit (and wrong) min_id settings.
Upstream ticket: https://fedorahosted.org/sssd/ticket/1014
Verified that the fixes are seen in the default sssd.conf file. Verified in version: # rpm -qi sssd | head Name : sssd Relocations: (not relocatable) Version : 1.5.1 Vendor: Red Hat, Inc. Release : 58.el6 Build Date: Sat 15 Oct 2011 12:14:26 AM IST Install Date: Mon 17 Oct 2011 08:50:14 PM IST Build Host: x86-001.build.bos.redhat.com Group : Applications/System Source RPM: sssd-1.5.1-58.el6.src.rpm Size : 3599114 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. New Contents: Cause: The example configuration file delivered with SSSD contained directives that were inaccurate, outdated or too low-level. Consequence: Users deriving their configuration from example configuration used non-optimal configurations and were getting confused. Fix: A new example configuration is provided. Result: Configuring SSSD with help of example configuration is not confusing.
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. http://rhn.redhat.com/errata/RHBA-2011-1529.html