Bug 163798 - [nsswitch.conf] nsswitch.conf with nss_ldap ignore [success=return]
Summary: [nsswitch.conf] nsswitch.conf with nss_ldap ignore [success=return]
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-03 19:10 UTC by Stephane D'Alu
Modified: 2017-12-31 22:32 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephane D'Alu 2012-01-03 19:10:09 UTC
when using nss_ldap with nsswitch.conf boot process get stuck when starting named. The name service trying to resolve "bind" user through "ldap" database despite a success in the "files" database

configuration used for nsswitch.conf is 
group: files [success=return] ldap
passwd: files [success=return] ldap

Was working fine in 9.0-RC3

Fix: 

in nss_ldap.conf:
nss_initgroups_ignoreusers root,ldap,bind
How-To-Repeat: install nss_ldap and configure nsswitch.conf to
group: files [success=return] ldap
passwd: files [success=return] ldap

try to start named
Comment 1 emz 2012-03-06 04:40:18 UTC
This isuue is like thousand years old. And it concerns every available 
backend, not just ldap. The same thing is with nss_winbind, for example. 
Furthermore, [success=return] is the default status/action pair. Plus, 
first I saw this issue on like 7.x. So I can say - 7.x and 8.x are 
affected too.

And I can say, this leads up to even more weird situation. Imagine 
OpenLDAP server running on a FreeBSD. After successful test we configure 
the same FreeBSD as LDAP client - from now on slapd will stuck on start, 
as it waits for itself.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:58:28 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped