LDAP Client

From Webmin Documentation
(Redirected from LDAPClient)
Jump to: navigation, search

This page explains why you would want to use LDAP, and how an LDAP Client system talks to an LDAP Server.

It allows you to select the LDAP Server that this client system will contact to in order to fetch user and group information. The most important field is the LDAP server hostnames, into which you must enter the hostname or IP address of the LDAP server on your network. If you have more than one replicated server, they can all be entered here.

The Login for non-root users and Password for non-root users fields must be filled in with a username and password accepted by the LDAP server, respectively. The login will typically be an LDAP distinguished name, like cn=Manager,dc=my-domain,dc=com.

Because this login and password is visible to all Unix users on your system, it is typically set to that of a LDAP user with limited privileges (such as read-only access, and no ability to view passwords). Because passwords do need to be checked in some situations, the Login for root user and Password for root user fields should be set to an LDAP username and password who has read access to the entire LDAP server. This second password is stored in a file that is only readable by the root user, and thus is secure from regular un-trusted Unix users.

Introduction to LDAP on Linux

LDAP is a network protocol that can be used to share databases of Unix users, groups and other information between multiple systems. Typically, a single LDAP server will store a databases of users, which is then queried by multiple clients. If these clients also mount home directories via NFS Exports and Disk and Network Filesystems, users will be able to login to any one of those systems with the same username and password. In many ways, LDAP is used similarly to NIS, covered on the NIS Client and Server page. Using a correctly configured LDAP Client it is possible to manage users and groups with LDAP Users and Groups.

LDAP Client install request

If the LDAP client software has not been installed correctly just click in the message displayed.

The LDAP Client module

LDAP Client Module

This module allows you to configure a Linux system as a client of an existing LDAP server. For this to work, your system must first have the packages require to act as a client installed - specifically the NSS LDAP client library, and the PAM client library. The actual package names differ depending on your distribution, but on Debian and Ubuntu they are libnss-ldap and libpam-ldap respectively. On Redhat and Fedora systems, they are both in the nss_ldap package. The simplest way to install these is to use the Software Packages module to install them direct from apt or yum.

Module Configuration

LDAP Client Module Configuration

On the server:

  • set LDAP client configuration files to /etc/openldap/slapd.d

Selecting an LDAP server

LDAP Client Server Configuration

Once you have the needed software installed, follow these steps to configure your system connect to the correct LDAP server:

  1. Open the LDAP Client module under System category. A page of icons as shown below will appear.
  2. Click on the LDAP Server Configuration icon to bring up the form below.
  3. In the LDAP server hostnames field, enter the hostname of your LDAP server. If you plan to use LDAP for address resolution (unlikely), enter the IP address instead.
  4. In the Login for non-root users field, enter the DN of a user in the LDAP database who has permission to read all information about users, such as cn=Manager,dc=my-domain,dc=com.
  5. In the Password for non-root users field, enter the password for the DN user above.
  6. Unless your LDAP server is running in SSL mode or on a custom port, all other options can be left as their defaults.
  7. Click the Save button.

Search bases

LDAP Client Search Bases

An LDAP database has a hierarchical structure, in many ways similar to Internet domain names. Each user or other object in the database has a full name (called the DN) that specifies its position in the hierarchy, like cn=moroder, cn=Users,dc=my-domain,dc=com. Typically, all the users in the database will be stored under the same parent DN, which would be dc=my-domain,dc=com in the previous example.

By default, all searches will be done under the Global search base. However, because most servers put users and groups under different sub-trees, you will probably need to set the Base for Unix users and Base for Unix groups to the distinguished names for those sub-trees. The Base for Unix passwords should be set to the same DN as Base for Unix users, as password information is almost always stored with other user attributes.

For your system to find users and groups in the LDAP database, it must know the DNs to search for them under. To configure this, do the following :

  1. Click on the LDAP Search Bases icon on the module's main page, which will bring up the form shown below.
  2. In the Global search base field, enter a DN like dc=my-domain, dc=com under which all your users and groups can be found.
  3. From the Search depth menu, select Entire subtree.
  4. Only if your DNs for users and groups are under completely different trees do you need to fill in the Base for Unix users and Base for Unix groups sections.
  5. Click Save.

Selecting services

LDAP Client Services

One more step is needed before your system will actually use LDAP to find users and groups - configuring the NSS (Name Service Switch) to use the LDAP datastore. To do this, following these steps :

  1. Click on the Services Using LDAP icon.
  2. In the table that appears, click on Unix users.
  3. Typically, only one data source will be selected initially - Files, which tells the system to use /etc/passwd to find user accounts. From the Second data source menu, select LDAP.
  4. Click Save. After returning to the services list, follow the same steps for the Unix shadow passwords and Unix groups services.

Once everything is configured, you can use the Validate Configuration button on the module's main page to check that everything is setup properly. If it reports any problems, you will need to re-try some of the steps above with different options.

LDAP Browser

Client Browser

This page provides a simple way of exploring the data in the currently configured LDAP server. It is useful for finding where in the hierarchy users and groups are stored, so that they can be correctly entered on the LDAP Search Bases page.