SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Using PAM should not be necessary. I haven't tinkered with LDAP yet, so I can only give a pointer. If everything is set up correctly, you should be able to use LDAP for authentication by configuring nsswitch via /etc/nsswitch.conf. The lines
Yep, you need nss_ldap, there is no good other way to make libc (and thus login) aware of LDAP for authentication. No need to run an LDAP server. Compiling nss_ldap and configuring ldap.conf should do the trick. openldap-clients is now in Slackware-Current, so you can download the SlackBuild from -current, and recompile it for 10.2 (I don't really know the LinuxPackages openldap package).
It should not be necessary to use PAM. If you use PAM, you will probably need other modules. Did you correctly configure /etc/ldap.conf ? Are there any relevant errors in the system logs? Is a connection to the LDAP server made?
You can check the last question by running
tcpdump -i <ethernet interface>
on one terminal, and trying to log in through LDAP on an other terminal.
also i made rc.openldap executable but it is not showing while system boots
If you want to authenticate against a LDAP server somewhere on your network, you do not need to run your own local LDAP server. So, there is no reason to run rc.openldap at boot.
When you put a "rc" script in /etc/rc.d and make it executable, that does not mean that the script will be automatically started by Slackware when your computer boots. You will need to add something like the following lines to /etc/rc.d/rc.local (I am taking your rc.openldap script as an example):
if [ -x /etc/rc.d/rc.openldap ]; then
echo "Starting LDAP server: /etc/rc.d/rc.oipenldap start"
That way, your script will run when Slackware boots (and it will show on the console). Disabling the script is as easy as "chmod -x rc.openldap"; you can leave the lines in rc.local intact.
Starting LDAP server: /etc/rc.d/rc.openldap start /etc/rc.d/rc.openldap: line 8: /usr/libexec/slapd: No such file or directory
i have installed "openldap-client-2.3.17-i486-1" downloaded from slack current
Now what did I tell you just before... you do not need to run rc.openldap because you only need the client functionality. The openldap-client package does not contain the slapd program (the server component).
About LDAP authentication in Slackware without using PAM: I know that this will not work with all LDAP servers. Try looking for more help, for instance on the alt.os.linux.slackware neewsgroup. I know of several regular posters there who have LDAP authentication on Slackware working.
If you can not get it to work at all, you might want to consider installing Dropline Gnome on your computer. Dropline will install PAM on your computer as well as Gnome.