Description of problem: F18 install with: authconfig --enablemd5 --enableshadow --enableldap --ldapserver=ldap.cora.nwra.com,ldap2.cora.nwra.com --ldapbasedn=dc=nwra,dc=com --enableldaptls --ldaploadcacert=http://www.cora.nwra.com/cgi-bin/getca.pl --enablekrb5 --krb5kdc=kerberos.cora.nwra.com,kerberos2.cora.nwra.com --krb5adminserver=kerberos.cora.nwra.com --krb5realm=CORA.NWRA.COM It configures sss for automount in nsswitch.conf and adds an [autofs] section to sssd.conf, but does not add "autofs" to the list of services: [sssd] services = nss, pam Version-Release number of selected component (if applicable): authconfig-6.2.4-2.fc18.x86_64
I'm not sure this is appropriate for authconfig, but we will need to configure sssd.conf to set: ldap_autofs_search_base = dc=cora,dc=nwra,dc=com in the [domain/default] section as well. It would be convenient to be able to set that with authconfig like we set the overall ldap_search_base with --ldapbasedn.
Is it a common requirement to set the ldap_autofs_search_base differently from the ldap_search_base? And does SSSD default to use the ldap_search_base if ldap_autofs_search_base is not set?
I really can't speak to how common it is. In our company's case we have multiple locations sharing common user area in "dc=nwra,dc=com", but each office has it's own automount maps for the local network configuration. My understanding is that it defaults to ldap_search_base if ldap_autofs_search_base is not set.
Fixed, however we don't set the ldap_autofs_search_base for now.