[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Getting started with LDAP
Adam Tauno Williams wrote:
>
> >Just getting started with another attempt at getting LDAP to give me some
> >functionality. The first time I attempted the install with an rpm and then
> >because the HOW-TO's are written from the perspective of a .tgz install I
>
> I highly recommend using the RPMS as their are some tricks to compiling OpenLDAP
> on Linux so that the specifics of Linux threads don't bit you in the a$$. slapd
> with Linux threads will periodically go bizerk, but slurpd needs threads, so you
> have to compile the two seperately and do a partial make install, etc....
>
> >tried that way and I failed again. I am attempting to follow the
> >directions
> >in http://www.openldap.org/faq/data/cache/180.html and I have edited my
> >slapd.conf file as follows
> >
>
> > #######################################################################
> > # ldbm database definitions
> > #######################################################################
> >
> > database ldbm
> > suffix "dc=samsrv, dc=vdrive"
> > rootdn "cn=dirk, dc=samsrv, dc=vdrive"
> > rootpw secret
> > directory /usr/tmp
> >
>
> Putting your LDAP database in /usr/tmp is a bad idea. You should create
> something like /var/spool/ldap with permissions so only root can access the
> directory and put you database there, or else any user/process and wipe it out.
Done
directory is now /var/spool/ldap
created directory. (permissions are 755) and edited slapd.conf.
>
> >My namesever on my server will resolve samsrv.vdrive so I believe these
> >would be the appropriate edits. Then I start the daemon from
> >/etc/rc.d/init.d/ldap start and it seems to be executing fine. The log
> >files evan tell me so. So then the next step would be to follow these
> >directions to add initial entries to the database.
> >http://www.openldap.org/faq/data/cache/182.html Here is the ldif file I
> >created: "my.ldif"
> >
> > dn: dc=samsrv, dc=vdrive
> > dc: samsrv
> > o: Home
> > objectclass: organization
> > objectclass: dcObject
> >
> > dn: cn=dirk, dc=samsrv, dc=vdrive
> > cn: dirk
> > sn: dirk
> > objectclass: person
> >
> > So the next step is to useldap add to add the entries.
> >
> >ldapadd -D "cn=dirk, dc=samsrv, dc=vdrive" -W < my.ldif
> >The reply to this command is a password request and after entering the
> >password the command returns as follows.
> >Enter LDAP Password:
> >ldap_bind: Can't contact LDAP server
>
> Yep, how about:
>
> ldapadd -D" cn=dirk, dc=samsrv, dc=vdrive" -w secret -f my.ldif
Nope, same error message
ldap_bind: Can't contact LDAP server
Is there a book in our library which discusses ldap. I missed the
presentation you did because I was driving into town from Baraga, MI.
This is confusing me; pop3 is on port 110 in /etc/services and runs from
inetd, ldap is running on port 389, if the slapd daemon is running (?not
working) my wife gets an error when checking for mail on the same server
using pop3. Is there something I need to edit in slapd.at.conf or
slapd.oc.conf?
I'm confused!!
So any ideas of what I should be looking for. I really have not edited much
for configuration from a standard rpm install. The error message is leaning
me towards an issue with name resolution. Could this be the problem? If my
domain is vdrive should I remove the reference to the server the daemon is
running on?
>
> >Part of this probably just comes from a lack of understanding on my part of
> >what functionality LDAP is going to give me. I'd like to start out by
> >getting it to give me mach roaming capabilities with netscape and then move
> >on to getting it to perform other tasks, possibly single server
> >authentication for both linux and windows computers. Frustration is
> >setting
> >in however with not getting past this point. Can someone tell me where my
> >mind aint right.
>
> The LDAP learning curve is more like a cliff.
>
> Systems and Network Administrator
> Morrison Industries
> 1825 Monroe Ave NW.
> Grand Rapids, MI. 49505