managed authentication</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
CLASS="CHAPTER"
><H1
><A
-NAME="PAM"
-></A
->Chapter 11. Configuring PAM for distributed but centrally
+NAME="PAM">Chapter 12. Configuring PAM for distributed but centrally
managed authentication</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN1825"
->11.1. Samba and PAM</A
-></H1
+NAME="AEN1788">12.1. Samba and PAM</H1
><P
>A number of Unix systems (eg: Sun Solaris), as well as the
xxxxBSD family and Linux, now utilize the Pluggable Authentication
><H1
CLASS="SECT1"
><A
-NAME="AEN1869"
->11.2. Distributed Authentication</A
-></H1
+NAME="AEN1832">12.2. Distributed Authentication</H1
><P
>The astute administrator will realize from this that the
combination of <TT
><H1
CLASS="SECT1"
><A
-NAME="AEN1876"
->11.3. PAM Configuration in smb.conf</A
-></H1
+NAME="AEN1839">12.3. PAM Configuration in smb.conf</H1
><P
>There is an option in smb.conf called <A
HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
The following is from the on-line help for this option in SWAT;</P
><P
>When Samba 2.2 is configure to enable PAM support (i.e.
-<CODE
+<TT
CLASS="CONSTANT"
->--with-pam</CODE
+>--with-pam</TT
>), this parameter will
control whether or not Samba should obey PAM's account
and session management directives. The default behavior