Cumulus Linux uses Pluggable Authentication Modules (PAM) and Name Service Switch (NSS) for user authentication.
NSS specifies the order of information sources used to resolve names for each service. Using this with authentication and authorization, it provides the order and location used for user lookup and group mapping on the system. PAM handles the interaction between the user and the system, providing login handling, session setup, authentication of users, and authorization of user actions.
NSS enables PAM to use LDAP to provide user authentication, group mapping, and information for other services on the system.
Configure LDAP Authentication
There are 3 common ways to configure LDAP authentication on Linux:
This chapter describes using
libnss-ldapd only. From internal testing, this library worked best with Cumulus Linux and is the easiest to configure, automate, and troubleshoot.
libpam-ldapd package depends on
nslcd. To install
ldap-utils, run the following command:
Follow the interactive prompts to answer questions about the LDAP URI, search base distinguished name (DN), and services that must have LDAP lookups enabled. This creates a very basic LDAP configuration using anonymous bind and initiates user search under the base DN specified.
Alternatively, you can pre-seed these parameters using the
debconf-utils. To use this method, run
apt-get install debconf-utils and create the pre-seeded parameters using
debconf-set-selections with the appropriate answers. Run
debconf-show <pkg> to check the settings. Here is an example of how to pre-seed answers to the installer questions using
After the install is complete, the name service LDAP caching daemon (
nslcd) runs. This service handles all of the LDAP protocol interactions and caches information returned from the LDAP server. In the
ldap is appended and is the secondary information source for passwd, group, and shadow. The local files (
/etc/shadow) are used first, as specified by the
compatas the first source in NSS for passwd, group, and shadow. This prevents you from getting locked out of the system.
After installation, you need to update the main configuration file (
/etc/nslcd.conf) to accommodate the expected LDAP server settings. The nslcd.conf man page details all the available configuration options. Some of the more important options relate to security and how the queries are handled.
The LDAP client starts a session by connecting to the LDAP server on TCP and UDP port 389, or on port 636 for LDAPS. Depending on the configuration, this connection might be unauthenticated (anonymous bind); otherwise, the client must provide a bind user and password. The variables used to define the connection to the LDAP server are the URI and bind credentials.
The URI is mandatory and specifies the LDAP server location using the FQDN or IP address. The URI also designates whether to use
ldap:// for clear text transport, or
ldaps:// for SSL/TLS encrypted transport. You can also specify an alternate port in the URI. Typically, in production environments, it is best to utilize the LDAPS protocol; otherwise, all communications are clear text and not secure.
After the connection to the server is complete, the BIND operation authenticates the session. The BIND credentials are optional, and if not specified, an anonymous bind is assumed. This is typically not allowed in most production environments. Configure authenticated (Simple) BIND by specifying the user (binddn) and password (bindpw) in the configuration. Another option is to use SASL (Simple Authentication and Security Layer) BIND, which provides authentication services using other mechanisms, like Kerberos. Contact your LDAP server administrator for this information as it depends on the configuration of the LDAP server and the credentials that are created for the client device.
When an LDAP client requests information about a resource, it must connect and bind to the server. Then, it performs one or more resource queries depending on the lookup. All search queries sent to the LDAP server are created using the configured search base, filter, and the desired entry (uid=myuser) being searched. If the LDAP directory is large, this search might take a significant amount of time. It is a good idea to define a more specific search base for the common maps (passwd and group).
It is also common to use search filters to specify criteria used when searching for objects within the directory. This is used to limit the search scope when authenticating users. The default filters applied are:
The map configuration allows you to override the attributes pushed from LDAP. To override an attribute for a given map, specify the attribute name and the new value. This is useful to ensure that the shell is bash and the home directory is
In LDAP, the map refers to one of the supported maps specified in the manpage for
nslcd.conf (such as passwd or group).
Here is an example configuration using Cumulus Linux.
nslcd Debug Mode
When setting up LDAP authentication for the first time, Cumulus Networks recommends you turn off the
nslcd service using the
systemctl stop nslcd.service command and run it in debug mode. Debug mode works whether you are using LDAP over SSL (port 636) or an unencrypted LDAP connection (port 389).
After you enable debug mode, run the following command to test LDAP queries:
If LDAP is configured correctly, the following messages appear after you run the
In the output above, <passwd(all)> indicates that the entire directory structure is queried.
You can query a specific user with the following command:
You can replace myuser with any username on the switch. The following debug output indicates that user myuser exists:
Notice how the
<passwd="myuser"> shows that the specific myuser user was queried.
The FQDN of the LDAP server URI does not match the FQDN in the CA-signed server certificate exactly.
nslcdcannot read the SSL certificate and reports a Permission denied error in the debug during server connection negotiation. Check the permission on each directory in the path of the root SSL certificate. Ensure that it is readable by the
nscd cachedaemon is also enabled and you make some changes to the user from LDAP, you can clear the cache using the following commands:
nscdpackage works with
nslcdto cache name entries returned from the LDAP server. This might cause authentication failures. To work around these issues:
- Try the authentication again.
The search filter returns wrong results. Check for typos in the search filter. Use
ldapsearchto test your filter.
Optionally, configure the basic LDAP connection and search parameters in
When a local username also exists in the LDAP database, the order of the information sources in
/etc/nsswitchcan be updated to query LDAP before the local user database. This is generally not recommended. For example, the configuration below ensures that LDAP is queried before the local database.
Configure LDAP Authorization
Linux uses the sudo command to allow non-administrator users (such as the default cumulus user account) to perform privileged operations. To control the users authorized to use sudo, the
/etc/sudoers file and files located in the
/etc/sudoers.d/ directory have a series of rules defined. Typically, the rules are based on groups, but can also be defined for specific users. Therefore, sudo rules can be added using the group names from LDAP. For example, if a group of users are associated with the group netadmin, you can add a rule to give those users sudo privileges. Refer to the sudoers manual (
man sudoers) for a complete usage description. Here's an illustration of this in
Active Directory Configuration
Active Directory (AD) is a fully featured LDAP-based NIS server created by Microsoft. It offers unique features that classic OpenLDAP servers lack. Therefore, it can be more complicated to configure on the client and each version of AD is a little different in how it works with Linux-based LDAP clients. Some more advanced configuration examples, from testing LDAP clients on Cumulus Linux with Active Directory (AD/LDAP), are available in our knowledge base.
LDAP Verification Tools
Typically, password and group information is retrieved from LDAP and cached by the LDAP client daemon. To test the LDAP interaction, you can use these command-line tools to trigger an LDAP query from the device. This helps to create the best filters and verify the information sent back from the LDAP server.
Identify a User with the id Command
id command performs a username lookup by following the lookup information sources in NSS for the passwd service. This simply returns the user ID, group ID and the group list retrieved from the information source. In the following example, the user cumulus is locally defined in
/etc/passwd, and myuser is on LDAP. The NSS configuration has the passwd map configured with the sources
getent command retrieves all records found with NSS for a given map. It can also get a specific entry under that map. You can perform tests with the passwd, group, shadow, or any other map configured in
/etc/nsswitch.conf. The output from this command is formatted according to the map requested. Therefore, for the passwd service, the structure of the output is the same as the entries in
/etc/passwd. The group map outputs the same structure as
/etc/group. In this example, looking up a specific user in the passwd map, the user cumulus is locally defined in
/etc/passwd, and myuser is only in LDAP.
In the next example, looking up a specific group in the group service, the group cumulus is locally defined in
/etc/groups, and netadmin is on LDAP.
Running the command
getent passwd or
getent group without a specific request returns all local and LDAP entries for the passwd and group maps.
ldapsearch command performs LDAP operations directly on the LDAP server. This does not interact with NSS. This command helps display what the LDAP daemon process is receiving back from the server. The command has many options. The simplest uses anonymous bind to the host and specifies the search DN and the attribute to look up.
There are several GUI LDAP clients available that help to work with LDAP servers. These are free tools to help show the structure of the LDAP database graphically.