[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: OpenLDAP <-> iPlanet cooperation
I don't know if this has anything to do with the OpenLDAP server as it
stands as you are using a Sun ONE solution to authenticate and the
problem is technically a Sun server problem since you cannot do that.
I suggest reading the Solaris Admin guide on NIS/NIS+/LDAP/FNS to
resolve your problems as they have some (okayish) migration scripts from
/etc/flat.files to LDAP for Sun ONE if you e-mail me offlist I know that
there is something that was entered into the automount maps from our
NIS+ stuff that need not be there, I can send you an excerpt from our
Sun LDAP server 5.1 if you wish, off-list ofcourse.
On Wed, 2003-02-12 at 07:31, Tibbetts, Ric wrote:
> Ok, since I've gotten no responses to this, I have to assume one of two
> things:
>
> 1) It's blatently, stupidly obvious, and I'm the only one who doesn't
> see it. Thus no one will answer.
>
> or
>
> 2) It doesn't make sense to anyone else either (maybe I didn't give
> enough info?), thus no one is answering.
>
> Please, if it's either of the above, just drop a note to say <shrug>
> dunno, or <mmbbwwaahahahahaaaaaa> That's so simple, RTFM...
> At least I'd have an indication of where to go next.
>
> Thank you!
>
> Ric
>
>
> Tibbetts, Ric wrote:
> > All;
> > I'm faced with a situation that I'm not sure how to resolve.
> > I need to set up Linux workstations to run autofs through LDAP.
> > Currently, the Suns are all set up that way.
> >
> > (prior to this project, I'd never worked with LDAP, so my knowledge on
> > the subject is extremely sparse).
> >
> > So far, I have a Linux client (running RedHat 8.0 + OpenLDAP), that
> > authenticates through the Sun based iPlanet Directory Server. It handles
> > logins just fine. But I can't get the automounter to work for home
> > directories.
> >
> > Per information I've found in various places, I've added the following
> > to /etc/auto.master
> >
> > /home
> > ldap:ldap.mlb.esid.northgrum.com:nisMapName=auto_home,dc=eng,dc=mlb,dc=northgrum,dc=com
> >
> >
> > starting autofs then produces the following in /var/log/messages:
> >
> > Feb 11 11:32:39 aurora automount[1336]: starting automounter version
> > 3.1.7, path = /home, maptype = ldap, mapname =
> > ldap.mlb.esid.northgrum.com:nisMapName=auto_home,dc=eng,dc=mlb,dc=northgrum,dc=com
> >
> > Feb 11 11:32:40 aurora autofs: automount startup succeeded
> > Feb 11 11:32:40 aurora automount[1336]: using kernel protocol version 3
> >
> > So far so good.
> >
> > So:
> >
> > #> service autofs status
> >
> > Configured Mount Points:
> > ------------------------
> > /usr/sbin/automount /home ldap
> > ldap.mlb.esid.northgrum.com:nisMapName=auto_home,dc=eng,dc=mlb,dc=northgrum,dc=com
> >
> >
> >
> > Active Mount Points:
> > --------------------
> > /usr/sbin/automount /home ldap
> > ldap.mlb.esid.northgrum.com:nisMapName=auto_home,dc=eng,dc=mlb,dc=northgrum,dc=com
> >
> >
> >
> > Great!
> >
> >
> > Then I try to log in:
> >
> > Feb 11 11:32:51 aurora login(pam_unix)[826]: session opened for user
> > tibberi by LOGIN(uid=0)
> > Feb 11 11:32:51 aurora automount[1336]: attempting to mount entry
> > /home/tibberi
> > Feb 11 11:32:52 aurora automount[1343]: lookup(ldap): query succeeded,
> > no matches for (&(objectclass=nisObject)(cn=/))
> > Feb 11 11:32:52 aurora automount[1343]: lookup(ldap): query succeeded,
> > no matches for (&(objectclass=automount)(cn=/))
> > Feb 11 11:32:52 aurora -- tibberi[826]: LOGIN ON tty3 BY tibberi
> >
> > Not so good. I get no home dir. What I don't understand is where the
> > cn=/ is coming from.
> > I've checked the LDAP server, and it shows that the line in auto.master
> > is a valid string.
> >
> > I don't know what's going wrong. Can someone shed some light on this?
> >
> > Much thanks in advance!
> >
> > Ric Tibbetts
> >
>