https://bugzilla.novell.com/show_bug.cgi?id=739078 https://bugzilla.novell.com/show_bug.cgi?id=739078#c0 Summary: Cannot authenticate via LDAP after switch to nslcd Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i586 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: lynn@steve-ss.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.2 (KHTML, like Gecko) Ubuntu/11.10 Chromium/15.0.874.106 Chrome/15.0.874.106 Safari/535.2 Having used Yast LDAP client to setup LDAP, switching to nss_pam_ldapd does not retain the settings in /etc/nsswitch.conf nor in /etc/pam.d/*. Settings in /etc/ldap.conf seem to conflict with settings in /etc/nslcd.conf. Reproducible: Always Steps to Reproduce: 1.Setup LDAP client using Yast 2.Authenticate via LDAP. 3.Install nss_pam_ldapd via yast and accept to remove nss_ldap. 4.Configure /etc/nslcd.conf with your own settings Actual Results: Cannot now authenticate via LDAP. Expected Results: Transparent migration from nss_ldap to nss_pam_ldapd. The files in /etc/pam.d seem to lose all references to LDAP when Yast LDAP Client is set to not use LDAP. The solution is to overwrite /etc/pam.d with a copy from before you disable LDAP in Yast LDAP Client. Would it be possible for Yast to make the switch to nslcd and preserve the pam settings? Maybe I should leave the Yast settings to 'Use LDAP', but then /etc/ldap.conf is used instead of /etc/nslcd.conf -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.