{
	"id": "392f4aa7-0573-470a-a767-2a459ad39e19",
	"created_at": "2026-04-06T00:22:27.576607Z",
	"updated_at": "2026-04-10T03:20:35.312909Z",
	"deleted_at": null,
	"sha1_hash": "75566eac451cb8716cb9ff030f79b7d3a5ab6e26",
	"title": "Chapter 2. Using Pluggable Authentication Modules (PAM) | Managing Single Sign-On and Smart Cards | Red Hat Enterprise Linux | 6",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 49837,
	"plain_text": "Chapter 2. Using Pluggable Authentication Modules (PAM) |\r\nManaging Single Sign-On and Smart Cards | Red Hat Enterprise\r\nLinux | 6\r\nArchived: 2026-04-05 17:33:56 UTC\r\nChapter 2. Using Pluggable Authentication Modules (PAM)\r\nPluggable authentication modules are a common framework for authentication and security. Both of Red Hat\r\nEnterprise Linux's single sign-on methods — Kerberos and smart cards — depend on underlying PAM\r\nconfiguration.\r\nUnderstanding and using PAM can be very beneficial for planning and implementing a secure, efficient single\r\nsign-on solution.\r\n2.1. About PAM\r\nCopy link\r\nPrograms that grant users access to a system use authentication to verify each other's identity (that is, to establish\r\nthat a user is who they say they are).\r\nHistorically, each program had its own way of authenticating users. In Red Hat Enterprise Linux, many programs\r\nare configured to use a centralized authentication mechanism called Pluggable Authentication Modules (\r\nPAM\r\n).\r\nPAM uses a pluggable, modular architecture, which affords the system administrator a great deal of flexibility in\r\nsetting authentication policies for the system. PAM is a useful system for developers and administrators for several\r\nreasons:\r\nPAM provides a common authentication scheme that can be used with a wide variety of applications.\r\nPAM provides significant flexibility and control over authentication for both system administrators and\r\napplication developers.\r\nPAM provides a single, fully-documented library which allows developers to write programs without\r\nhaving to create their own authentication schemes.\r\nhttps://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/managing_smart_cards/pluggable_authentication_modules\r\nPage 1 of 2\n\nPAM has an extensive documentation set with much more detail about both using PAM and writing modules to\r\nextend or integrate PAM with other applications. Almost all of the major modules and configuration files with\r\nPAM have their own manpages. Additionally, the /usr/share/doc/pam- version# directory contains a System\r\nAdministrators' Guide, a Module Writers' Manual, and the Application Developers' Manual, as well as a copy of\r\nthe PAM standard, DCE-RFC 86.0.\r\nThe libraries for PAM are available at http://www.kernel.org/pub/linux/libs/pam/. This is the primary distribution\r\nwebsite for the Linux-PAM project, containing information on various PAM modules, frequently asked questions,\r\nand additional PAM documentation.\r\nSource: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/managing_smart_cards/pluggable_authentication_mod\r\nules\r\nhttps://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/managing_smart_cards/pluggable_authentication_modules\r\nPage 2 of 2",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/managing_smart_cards/pluggable_authentication_modules"
	],
	"report_names": [
		"pluggable_authentication_modules"
	],
	"threat_actors": [],
	"ts_created_at": 1775434947,
	"ts_updated_at": 1775791235,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/75566eac451cb8716cb9ff030f79b7d3a5ab6e26.pdf",
		"text": "https://archive.orkl.eu/75566eac451cb8716cb9ff030f79b7d3a5ab6e26.txt",
		"img": "https://archive.orkl.eu/75566eac451cb8716cb9ff030f79b7d3a5ab6e26.jpg"
	}
}