Chapter 16. Pluggable Authentication Modules (PAM)

Chapter 16. Pluggable Authentication Modules (PAM)

16.1. Advantages of PAM
16.2. PAM Configuration Files
16.2.1. PAM Service Files
16.3. PAM Configuration File Format
16.3.1. Module Interface
16.3.2. Control Flag
16.3.3. Module Name
16.3.4. Module Arguments
16.4. Sample PAM Configuration Files
16.5. Creating PAM Modules
16.6. PAM and Administrative Credential Caching
16.6.1. Removing the Timestamp File
16.6.2. Common pam_timestamp Directives
16.7. PAM and Device Ownership
16.7.1. Device Ownership
16.7.2. Application Access
16.8. Additional Resources
16.8.1. Installed Documentation
16.8.2. Useful Websites

Programs which grant users access to a system verify each user's identity through a process called authentication. Historically, each such program had its own way of performing the task of authentication. Under Red Hat Enterprise Linux, many such programs are configured to use a centralized authentication mechanism called Pluggable Authentication Modules or PAM.

PAM uses a pluggable, modular architecture, which affords the system administrator a great deal of flexibility in setting authentication policies for the system.

In most situations, the default PAM configuration file for a PAM-aware application is sufficient. However, sometimes it may become necessary to edit a PAM configuration file. Because misconfiguration of PAM can compromise system security, it is important to understand the structure of these files before making any modifications (refer to Section 16.3, “PAM Configuration File Format” for more information).