Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Nov 2004 17:40:20 -0500
From:      Jon Adams <jkadams@computer.org>
To:        Cezar Fistik <cezar@arax.md>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Looking for a good NSS/Pam_LDAP/Open LDAP how-to for 5.x
Message-ID:  <41A11954.4040403@computer.org>
In-Reply-To: <1745259853.20041121161820@arax.md>
References:  <41A0952B.4010107@computer.org> <1745259853.20041121161820@arax.md>

next in thread | previous in thread | raw e-mail | index | archive | help


Cezar Fistik wrote:

>Hello Jon,
>
>Sunday, November 21, 2004, 3:16:27 PM, you wrote:
>
>JA> I tried this one:
>JA> http://www.cultdeadsheep.org/FreeBSD/docs/Quick_and_dirty_FreeBSD_5_x_and_nss_ldap_mini-HOWTO.html
>
>JA> and it emphatically does not work, and I followed it to the letter.... I
>JA> think it has something to do with NSS only using SSL/port 636.
>
>JA> so then I tried it with that added.... still no dice
>
>I followed the above howto word by word too and it didn't work from
>the first try. So I made some searches, I think on pamldap or on
>openldap mailing lists, don't remember exactly, and found another
>explanation on how to set things up. As far as I remember, my problem
>was with ldap.conf and nss_ldap.conf files which reside in
>/usr/local/etc/. This files must be identical, so you may symlink
>them, as I did. After that everything started to work, in my case ssh
>through pam_ldap.
>  
>
I found this to be the case also....  I didnt think to symlink them 
though (Doh)

>Unfortunately, my detailed configs are at work, so if you won't find
>anything I'll post them on monday.
>  
>
would greatly appreciate it....  I cant get ssh logins (or any others) 
to work... really frustrating...

Thanks...

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41A11954.4040403>