This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Pluggable Authentication Modules
Pluggable Authentication Modules

Version management

Difference between version and

At line 1 added 75 lines
!!! Overview
[{$pagename}] ([PAM]) is an [Authentication Method] to integrate multiple low-level authentication schemes into a high-level API, which allows for programs that rely on authentication to be written independently of the underlying authentication scheme.
The [{$pagename}] framework provides a uniform way for authentication-related activities to take place. This approach enables application developers to use PAM services without having to know the semantics of the policy. Algorithms are centrally supplied. The algorithms can be modified independently of the individual applications. With PAM, administrators can tailor the authentication process to the needs of a particular system without having to change any applications. Adjustments are made through pam.conf, the PAM configuration file.
The following figure illustrates the PAM architecture. Applications communicate with the PAM library through the PAM application programming interface (API). PAM modules communicate with the PAM library through the PAM service provider interface (SPI). Thus, the PAM library enables applications and modules to communicate with each other.
[{Image src='Pluggable Authentication Modules/pam.overview.1.png' width='..' height='..' align='left|center|right' style='..' class='..' }]
!!![PAM Configuration file syntax|PAMConfigurationFileSyntax]
!![PAM Service Types]
There are four [PAM Service Types]
!! [PAM Control Flags|PAM Control]
All PAM modules generate a success or failure result when checked. [PAM Control Flags|PAM Control] flags tell PAM what do with the result.
!![PAM module-arguments]
[{$pagename}] utilizes [PAM module-arguments] to pass information to a pluggable module during authentication for a particular [PAM Service Types].
!![PAM module|PAM Module Name]
!!History
[Pluggable authentication modules or PAM|http://en.wikipedia.org/wiki/Pluggable_Authentication_Modules] are a mechanism to integrate multiple low-level authentication schemes into a high-level API, which allows for programs that rely on authentication to be written independently of the underlying authentication scheme.
Our interest in [{$pagename}] is for the setup of [LDAP for Linux and Unix Clients].
!!!PAM Documentation
*[SUN's PAM page|http://wwws.sun.com/software/solaris/pam/]
*[Linux PAM Pages|http://www.kernel.org/pub/linux/libs/pam/]
*[OpenPam|http://www.openpam.org/]
*[Java-PAM Bridge|http://jpam.sourceforge.net/]
!!!PAM Implementations
This information is __*OLD*__
This is of course not current, but is provided to show the many differences.
||Distribution||Version||PAM-Version||Features||Release Date
|SuSE Linux Enterprise Server|8|0.76| |July2002
| |9|.077|Some third party modules|September 2002
| |9.3|0.77|Some third party modules|December 2005
| |10|0.99.3| |January 2006
|Red Hat Enterprise Linux|3.6|0.75| |April 2001
| |4|0.77| |September 2002
| |4.4|0.77|newer build|April 2006
|Fedora Core|5|0.78| |November 2004
| |6|0.99.6.2| |November 2006
|Debian GNU/Linux|3.1.2|0.76|Many Third Party Modules|July 2002
| |4.0|0.79|Many Third Party Modules|December 2006
|Ubunta Linux|5.10|0.75|Many Third Party Modules|October 2005
| |6.06|0.77|Many Third Party Modules|July 2006
| |6.10|0.79|Many Third Party Modules|November 2006
|Arch Linux|0.7.1|0.81| |November 2005
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop