[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: problems using ldapsearch with 2.0

Ok.  That was correct.  I didn't have the rights.  When I used -D
cn=manager,dc=nowcom,dc=com -W and entered a password, it came back with the
correct information.  What do you suppose is the best way to allow hosts to
contact the ldap server so that users can authenticate against it?

If I put in the rootdn: cn=manager,dc=nowcom,dc=com   and passwd   secret (for
example) into /etc/ldap.conf, then I can authenticate against it, otherwise I
can't do it.

Is there an acl that I can include in order to allow hosts to authenticate my
users?   I will, btw, be eventually tieing this authentication into Samba so
Windows users will also have to authenticate against it to log into the

Hugo.van.der.Kooij@caiw.nl said:

> On Fri, 22 Sep 2000, Joseph Hoot wrote:
> > Ok.  I'm almost done asking all these questions on the mailing list.  Kurt
> > Hugo, you have both helped me a great deal.  I appreciate it very much.
> > 
> > in openldap 1.2.11 I could do "ldapsearch uid=jhoot", for example, and it
> > would find my user jhoot and print out all of his details.  I try the same
> > command in 2.0 and I don't see anything.  Here is my entry in the
> Retry but now use the -D option for the manager (like you used in ldapadd)
> and see if it is listed.
> In that case you don't seem to have the rights to query it anonymous.
> (which is the default.)
> Hugo.
> -- 
> Hugo van der Kooij; Oranje Nassaustraat 16; 3155 VJ  Maasland
> hvdkooij@caiw.nl	http://home.kabelfoon.nl/~hvdkooij/
> --------------------------------------------------------------
> Quoting this tagline is illegal! (http://www.dtcc.edu/cs/rfc1855.html)

Joseph Hoot
System Administrator