Bug 103461
Summary: | local root login failure when LDAP server is not reachable | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <redhat> |
Component: | nss_ldap | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED DUPLICATE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 8.0 | CC: | mattdm, srevivo, tjarls |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:58:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2003-08-31 10:48:54 UTC
Btw: this works around the problem, but IMHO the entries in nsswitch.conf file should be followed, the "files" should preceed over "ldap". in /etc/pam.d/system-auth, add "authinfo_unavail=ignore" option: Original line: ###account [default=bad success=ok user_unknown=ignore service_err=ignore system_err=ignore] /lib/security/pam_ldap.so New line: account [default=bad success=ok user_unknown=ignore service_err=ignore system_err=ignore authinfo_unavail=ignore] /lib/security/pam_ldap.so This work around did not work for me. In addition I had to insert the following line between "account .. pam_unix.so" and "account .. pam_ldap.so": account sufficient /lib/security/$ISA/pam_localuser.so Shouldn't this be reported under authconfig instead of nss_ldap? I should have checked before comenting on this bug. Bug 118239 offers the same fix in a more detailed way. Also the same bug seems to have been reported many times: #55193 #63631 #63717 #77575 #86606 Still present in Fedora Core 2 test 2 *** This bug has been marked as a duplicate of 55193 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |