The timeouts are how long to wait for ldap to respond. It should check local (normally via pam) next.
We have our user's in LDAP and can still login using the local accounts. Your issue isn't an LDAP problem, it's a pam/nsswitch/local issue. - chris Chris Jacobs Systems Administrator, Technology Services Group Apollo Group | Apollo Marketing & Product Development | Aptimus, Inc. 1501 4th Ave | Suite 2500 | Seattle, WA 98101 direct 206.839.8245 | cell 206.601.3256 | Fax 206.644.0628 email: [email protected] ________________________________ From: [email protected] <[email protected]> To: Michael Starling <[email protected]> Cc: openldap <[email protected]> Sent: Thu Mar 22 18:10:55 2012 Subject: Re: Root not allowed to login Hi Michael, I have changed the timelimit and bind_timelimit to 4 but it still checks with ldap immediately ( I mean when root logs in ). i doubt it has anything to do with the time because it checks immediately without any delay. On Thu, Mar 22, 2012 at 9:51 PM, Michael Starling <[email protected]<mailto:[email protected]>> wrote: Try setting your timelimt and bind_timelimit to something like a bit lower. timelimit 4 bind_timelimit 4 ________________________________ Date: Thu, 22 Mar 2012 17:03:56 +0800 Subject: Root not allowed to login From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Hi, My client is installed with RHEL 6.0 and I am using OpenLDAP 2.4. When the box loses connection with the ldap server, even the root cannot log in as it tries to bind with the ldap server. This can be seen when I log in with root and the message below appears : sshd: pam_ldap: error trying to bind as user "uid=root, ou=People, dc=example,dc=com" (Invalid credentials). My root user is not even in the ldap database. When connection is fine, the message above does not affect the login of root. The login of root is only screwed up when the box loses connectivity. Attached are my pam.d/system-auth file, pam.d/login, pam./dsshd and ldap.conf files. I have been googling around but some either switch to kerberos, or the question is left unatttended to. Please help. I can only resort to restarting the box whenever this happens. How can I configure the ldap so that local users can login when there's no connectivity to ldap server? Thanks heaps! -- ________________________________ MGRC - Sequence. Analyse. Innovate. Su Seau Yeen Manager, IT Operations Malaysian Genomics Resource Centre Berhad (MGRC) T: +6 03 2283 1820<tel:%2B6%C2%A003%C2%A02283%C2%A01820> | F: +6 03 2282 8102<tel:%2B6%C2%A003%C2%A02282%C2%A08102> | M: +6 012 6784642<tel:%2B6%C2%A0012%C2%A06784642> | www.mgrc.com.my<http://www.mgrc.com.my/> ________________________________ This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient, is strictly prohibited. If you receive this e-mail in error, please contact us immediately by return e-mail and delete the original message(s). -- ________________________________ MGRC - Sequence. Analyse. Innovate. Su Seau Yeen Manager, IT Operations Malaysian Genomics Resource Centre Berhad (MGRC) T: +6 03 2283 1820 | F: +6 03 2282 8102 | M: +6 012 6784642 | www.mgrc.com.my<http://www.mgrc.com.my/> ________________________________ This e-mail is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient, is strictly prohibited. If you receive this e-mail in error, please contact us immediately by return e-mail and delete the original message(s). ________________________________ This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
