Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
05-28-2014, 07:55 AM
|
#1
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
|
LDAP authentication : Slackware server vs. Ubuntu client?
Hi,
As far as I know, LDAP authentication is not used in practice on Slackware due to the lack of PAM. That's a field I'm not familiar with, and I have a general question. If my client machines are running Ubuntu (more exactly ElementaryOS 0.2, an excellent Ubuntu 12.04 derivative), can I setup LDAP authentication against a Slackware server without having to jump through burning loops? Is it only the client machine that has to be "PAMified"?
Cheers,
Niki
|
|
|
05-28-2014, 08:11 AM
|
#2
|
LQ Guru
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,339
|
Slackware by default ships only openldap-client, so you should build yourself an openldap-server package (in the example linked the openldap-client SlackBuild is taken as base): you can see here for an example of slapd.conf.
That should suffice for just authenticating against the server.
|
|
|
05-28-2014, 01:37 PM
|
#3
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
Original Poster
|
Quote:
Originally Posted by ponce
Slackware by default ships only openldap-client, so you should build yourself an openldap-server package (in the example linked the openldap-client SlackBuild is taken as base): you can see here for an example of slapd.conf.
That should suffice for just authenticating against the server.
|
On the server, do I also have to build Linux-PAM, pam_ldap, nss_ldap and shadow, as described in the article ?
|
|
|
05-28-2014, 01:41 PM
|
#4
|
LQ Guru
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,339
|
no.
supposing you don't have any services (http or whatever) running on it that need to authenticate on the ldap server running on the same box, those are just for the clients that need to authenticate logins on the server (but you are better off integrating that stuff with vbatts' work with PAM).
in this scenario, you just do ldap queries on the server, so PAM isn't involved.
Last edited by ponce; 05-28-2014 at 02:14 PM.
|
|
1 members found this post helpful.
|
05-28-2014, 03:10 PM
|
#5
|
MLED Founder
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453
Original Poster
|
OK thanks !
|
|
|
All times are GMT -5. The time now is 05:55 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|