Changeset 134 for branches/samba-3.0/docs/htmldocs/Samba3-HOWTO/passdb.html
- Timestamp:
- May 23, 2008, 6:56:41 AM (17 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/samba-3.0/docs/htmldocs/Samba3-HOWTO/passdb.html
r44 r134 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 11. Account Information Databases</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"><link rel="start" href="index.html" title="The Official Samba-3 HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="NetworkBrowsing.html" title="Chapter 10. Network Browsing"><link rel="next" href="groupmapping.html" title="Chapter 12. Group Mapping: MS Windows and UNIX"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 11. Account Information Databases</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="groupmapping.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="passdb"></a>Chapter 11. Account Information Databases</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:jra@samba.org">jra@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span><div class="affiliation"><span class="orgname">SuSE<br></span><div class="address"><p><code class="email"><<a href="mailto:gd@suse.de">gd@suse.de</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Olivier (lem)</span> <span class="surname">Lemaire</span></h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><code class="email"><<a href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>></code></p></div></div></div></div><div><p class="pubdate">May 24, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="passdb.html#id351371">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id351406">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id351576">New Account Storage Systems</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#passdbtech">Technical Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id352102">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id352583">Mapping User Identifiers between MS Windows and UNIX</a></span></dt><dt><span class="sect2"><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></span></dt><dt><span class="sect2"><a href="passdb.html#id353101">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id353484">LDAP Directories and Windows Computer Accounts</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#acctmgmttools">Account Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id353897">The <code class="literal">smbpasswd</code> Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The <code class="literal">pdbedit</code> Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id356265">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id356336">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id356408">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id356653">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id356799">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id359200">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id359206">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id359237">Configuration of <em class="parameter"><code>auth methods</code></em></a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id351186"></a> 3 <a class="indexterm" name="id351193"></a> 4 <a class="indexterm" name="id351200"></a> 5 <a class="indexterm" name="id351206"></a> 6 Samba-3 implements a new capability to work concurrently with multiple account backends. 7 The possible new combinations of password backends allows Samba-3 a degree of flexibility 8 and scalability that previously could be achieved only with MS Windows Active Directory (ADS). 9 This chapter describes the new functionality and how to get the most out of it. 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 11. Account Information Databases</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="NetworkBrowsing.html" title="Chapter 10. Network Browsing"><link rel="next" href="groupmapping.html" title="Chapter 12. Group Mapping: MS Windows and UNIX"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 11. Account Information Databases</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="groupmapping.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="passdb"></a>Chapter 11. Account Information Databases</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span> <div class="affiliation"><span class="orgname">SuSE<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:gd@suse.de">gd@suse.de</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Olivier (lem)</span> <span class="surname">Lemaire</span></h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>></code></p></div></div></div></div><div><p class="pubdate">May 24, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="passdb.html#id374429">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id374464">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id374634">New Account Storage Systems</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#passdbtech">Technical Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id375167">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id375648">Mapping User Identifiers between MS Windows and UNIX</a></span></dt><dt><span class="sect2"><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></span></dt><dt><span class="sect2"><a href="passdb.html#id376168">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id376546">LDAP Directories and Windows Computer Accounts</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#acctmgmttools">Account Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id376958">The <code class="literal">smbpasswd</code> Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The <code class="literal">pdbedit</code> Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id379310">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id379357">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id379428">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id379677">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id379822">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id382162">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id382168">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id382202">Configuration of <em class="parameter"><code>auth methods</code></em></a></span></dt></dl></dd></dl></div><p> 2 <a class="indexterm" name="id374245"></a> 3 <a class="indexterm" name="id374251"></a> 4 <a class="indexterm" name="id374258"></a> 5 <a class="indexterm" name="id374265"></a> 6 Early releases of Samba-3 implemented new capability to work concurrently with multiple account backends. This 7 capability was removed beginning with release of Samba 3.0.23. Commencing with Samba 3.0.23 it is possible to 8 work with only one specified passwd backend. 10 9 </p><p> 11 <a class="indexterm" name="id3 51219"></a>12 <a class="indexterm" name="id3 51226"></a>13 <a class="indexterm" name="id3 51233"></a>14 <a class="indexterm" name="id3 51240"></a>15 <a class="indexterm" name="id3 51246"></a>16 <a class="indexterm" name="id3 51253"></a>10 <a class="indexterm" name="id374277"></a> 11 <a class="indexterm" name="id374284"></a> 12 <a class="indexterm" name="id374291"></a> 13 <a class="indexterm" name="id374298"></a> 14 <a class="indexterm" name="id374304"></a> 15 <a class="indexterm" name="id374311"></a> 17 16 The three passdb backends that are fully maintained (actively supported) by the Samba Team are: 18 17 <code class="literal">smbpasswd</code> (being obsoleted), <code class="literal">tdbsam</code> (a tdb-based binary file format), … … 25 24 <code class="literal">ldapsam</code> for larger and more complex networks. 26 25 </p><p> 27 <a class="indexterm" name="id3 51318"></a>28 <a class="indexterm" name="id3 51325"></a>29 <a class="indexterm" name="id3 51332"></a>30 <a class="indexterm" name="id3 51339"></a>31 <a class="indexterm" name="id3 51346"></a>32 <a class="indexterm" name="id3 51352"></a>33 <a class="indexterm" name="id3 51359"></a>26 <a class="indexterm" name="id374376"></a> 27 <a class="indexterm" name="id374383"></a> 28 <a class="indexterm" name="id374390"></a> 29 <a class="indexterm" name="id374397"></a> 30 <a class="indexterm" name="id374404"></a> 31 <a class="indexterm" name="id374410"></a> 32 <a class="indexterm" name="id374417"></a> 34 33 In a strict and literal sense, the passdb backends are account storage mechanisms (or methods) alone. The choice 35 34 of terminology can be misleading, however we are stuck with this choice of wording. This chapter documents the … … 37 36 machine trust accounts (computer accounts) and interdomain trust accounts. These are all treated as user-like 38 37 entities. 39 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3 51371"></a>Features and Benefits</h2></div></div></div><p>38 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id374429"></a>Features and Benefits</h2></div></div></div><p> 40 39 Samba-3 provides for complete backward compatibility with Samba-2.2.x functionality 41 40 as follows: 42 <a class="indexterm" name="id3 51380"></a>43 <a class="indexterm" name="id3 51389"></a>44 <a class="indexterm" name="id3 51398"></a>45 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 51406"></a>Backward Compatibility Account Storage Systems</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Plaintext</span></dt><dd><p>46 <a class="indexterm" name="id3 51423"></a>47 <a class="indexterm" name="id3 51430"></a>48 <a class="indexterm" name="id3 51437"></a>49 <a class="indexterm" name="id3 51443"></a>50 <a class="indexterm" name="id3 51450"></a>41 <a class="indexterm" name="id374438"></a> 42 <a class="indexterm" name="id374447"></a> 43 <a class="indexterm" name="id374456"></a> 44 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id374464"></a>Backward Compatibility Account Storage Systems</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Plaintext</span></dt><dd><p> 45 <a class="indexterm" name="id374481"></a> 46 <a class="indexterm" name="id374488"></a> 47 <a class="indexterm" name="id374495"></a> 48 <a class="indexterm" name="id374501"></a> 49 <a class="indexterm" name="id374508"></a> 51 50 This isn't really a backend at all, but is listed here for simplicity. Samba can be configured to pass 52 51 plaintext authentication requests to the traditional UNIX/Linux <code class="filename">/etc/passwd</code> and 53 52 <code class="filename">/etc/shadow</code>-style subsystems. On systems that have Pluggable Authentication Modules 54 53 (PAM) support, all PAM modules are supported. The behavior is just as it was with Samba-2.2.x, and the 55 protocol limitations imposed by MS Windows clients apply likewise. Please refer to <a href="passdb.html#passdbtech" title="Technical Information">Technical Information</a>, for more information regarding the limitations of plaintext54 protocol limitations imposed by MS Windows clients apply likewise. Please refer to <a class="link" href="passdb.html#passdbtech" title="Technical Information">Technical Information</a>, for more information regarding the limitations of plaintext 56 55 password usage. 57 56 </p></dd><dt><span class="term">smbpasswd</span></dt><dd><p> 58 <a class="indexterm" name="id3 51493"></a>59 <a class="indexterm" name="id3 51500"></a>60 <a class="indexterm" name="id3 51507"></a>61 <a class="indexterm" name="id3 51514"></a>57 <a class="indexterm" name="id374551"></a> 58 <a class="indexterm" name="id374558"></a> 59 <a class="indexterm" name="id374565"></a> 60 <a class="indexterm" name="id374572"></a> 62 61 This option allows continued use of the <code class="filename">smbpasswd</code> 63 62 file that maintains a plain ASCII (text) layout that includes the MS Windows … … 65 64 account information. This form of password backend does not store any of 66 65 the MS Windows NT/200x SAM (Security Account Manager) information required to 67 provide the extended controls that are needed for more comprehensive 66 provide the extended controls that are needed for more comprehensive 68 67 interoperation with MS Windows NT4/200x servers. 69 68 </p><p> … … 71 70 versions of Samba. It may be deprecated in future releases. 72 71 </p></dd><dt><span class="term">ldapsam_compat (Samba-2.2 LDAP Compatibility)</span></dt><dd><p> 73 <a class="indexterm" name="id3 51547"></a>74 <a class="indexterm" name="id3 51554"></a>75 <a class="indexterm" name="id3 51561"></a>72 <a class="indexterm" name="id374605"></a> 73 <a class="indexterm" name="id374612"></a> 74 <a class="indexterm" name="id374619"></a> 76 75 There is a password backend option that allows continued operation with 77 76 an existing OpenLDAP backend that uses the Samba-2.2.x LDAP schema extension. … … 79 78 no reason to force migration at this time. This tool will eventually 80 79 be deprecated. 81 </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 51576"></a>New Account Storage Systems</h3></div></div></div><p>80 </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id374634"></a>New Account Storage Systems</h3></div></div></div><p> 82 81 Samba-3 introduces a number of new password backend capabilities. 83 <a class="indexterm" name="id3 51584"></a>84 <a class="indexterm" name="id3 51593"></a>82 <a class="indexterm" name="id374642"></a> 83 <a class="indexterm" name="id374651"></a> 85 84 </p><div class="variablelist"><dl><dt><span class="term">tdbsam</span></dt><dd><p> 86 <a class="indexterm" name="id3 51614"></a>87 <a class="indexterm" name="id3 51621"></a>88 <a class="indexterm" name="id3 51628"></a>85 <a class="indexterm" name="id374672"></a> 86 <a class="indexterm" name="id374679"></a> 87 <a class="indexterm" name="id374686"></a> 89 88 This backend provides a rich database backend for local servers. This 90 89 backend is not suitable for multiple domain controllers (i.e., PDC + one 91 90 or more BDC) installations. 92 91 </p><p> 93 <a class="indexterm" name="id3 51639"></a>94 <a class="indexterm" name="id3 51646"></a>95 <a class="indexterm" name="id3 51653"></a>96 <a class="indexterm" name="id3 51659"></a>97 <a class="indexterm" name="id3 51666"></a>98 <a class="indexterm" name="id3 51673"></a>92 <a class="indexterm" name="id374697"></a> 93 <a class="indexterm" name="id374704"></a> 94 <a class="indexterm" name="id374711"></a> 95 <a class="indexterm" name="id374717"></a> 96 <a class="indexterm" name="id374724"></a> 97 <a class="indexterm" name="id374731"></a> 99 98 The <span class="emphasis"><em>tdbsam</em></span> password backend stores the old <span class="emphasis"><em> 100 99 smbpasswd</em></span> information plus the extended MS Windows NT/200x … … 104 103 with MS Windows NT4/200x-based systems. 105 104 </p><p> 106 <a class="indexterm" name="id3 51693"></a>107 <a class="indexterm" name="id3 51700"></a>108 <a class="indexterm" name="id3 51707"></a>105 <a class="indexterm" name="id374751"></a> 106 <a class="indexterm" name="id374758"></a> 107 <a class="indexterm" name="id374765"></a> 109 108 The inclusion of the <span class="emphasis"><em>tdbsam</em></span> capability is a direct 110 109 response to user requests to allow simple site operation without the overhead … … 113 112 the use of OpenLDAP or of Active Directory integration is strongly recommended. 114 113 </p></dd><dt><span class="term">ldapsam</span></dt><dd><p> 115 <a class="indexterm" name="id3 51732"></a>116 <a class="indexterm" name="id3 51739"></a>117 This provides a rich directory backend for distributed account installation. 114 <a class="indexterm" name="id374790"></a> 115 <a class="indexterm" name="id374797"></a> 116 This provides a rich directory backend for distributed account installation. 118 117 </p><p> 119 <a class="indexterm" name="id3 51750"></a>120 <a class="indexterm" name="id3 51757"></a>121 <a class="indexterm" name="id3 51764"></a>122 <a class="indexterm" name="id3 51770"></a>123 <a class="indexterm" name="id3 51777"></a>118 <a class="indexterm" name="id374808"></a> 119 <a class="indexterm" name="id374815"></a> 120 <a class="indexterm" name="id374822"></a> 121 <a class="indexterm" name="id374828"></a> 122 <a class="indexterm" name="id374835"></a> 124 123 Samba-3 has a new and extended LDAP implementation that requires configuration 125 124 of OpenLDAP with a new format Samba schema. The new format schema file is 126 125 included in the <code class="filename">examples/LDAP</code> directory of the Samba distribution. 127 126 </p><p> 128 <a class="indexterm" name="id3 51797"></a>129 <a class="indexterm" name="id3 51804"></a>130 <a class="indexterm" name="id3 51811"></a>131 <a class="indexterm" name="id3 51818"></a>132 <a class="indexterm" name="id3 51825"></a>127 <a class="indexterm" name="id374855"></a> 128 <a class="indexterm" name="id374862"></a> 129 <a class="indexterm" name="id374869"></a> 130 <a class="indexterm" name="id374876"></a> 131 <a class="indexterm" name="id374883"></a> 133 132 The new LDAP implementation significantly expands the control abilities that 134 133 were possible with prior versions of Samba. It is now possible to specify … … 137 136 requests both for capability and greater scalability. 138 137 </p></dd></dl></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="passdbtech"></a>Technical Information</h2></div></div></div><p> 139 <a class="indexterm" name="id3 51856"></a>140 <a class="indexterm" name="id3 51863"></a>138 <a class="indexterm" name="id374914"></a> 139 <a class="indexterm" name="id374921"></a> 141 140 Old Windows clients send plaintext passwords over the wire. Samba can check these 142 141 passwords by encrypting them and comparing them to the hash stored in the UNIX user database. 143 142 </p><p> 144 <a class="indexterm" name="id3 51874"></a>145 <a class="indexterm" name="id3 51881"></a>146 <a class="indexterm" name="id3 51888"></a>147 <a class="indexterm" name="id3 51895"></a>143 <a class="indexterm" name="id374932"></a> 144 <a class="indexterm" name="id374939"></a> 145 <a class="indexterm" name="id374946"></a> 146 <a class="indexterm" name="id374953"></a> 148 147 Newer Windows clients send encrypted passwords (LanMan and NT hashes) instead of plaintext passwords over 149 148 the wire. The newest clients will send only encrypted passwords and refuse to send plaintext passwords unless 150 149 their registry is tweaked. 151 150 </p><p> 152 <a class="indexterm" name="id3 51907"></a>153 <a class="indexterm" name="id3 51914"></a>151 <a class="indexterm" name="id374965"></a> 152 <a class="indexterm" name="id374972"></a> 154 153 Many people ask why Samba cannot simply use the UNIX password database. Windows requires 155 passwords that are encrypted in its own format. The UNIX passwords can't be converted to 154 passwords that are encrypted in its own format. The UNIX passwords can't be converted to 156 155 UNIX-style encrypted passwords. Because of that, you can't use the standard UNIX user 157 156 database, and you have to store the LanMan and NT hashes somewhere else. 158 157 </p><p> 159 <a class="indexterm" name="id3 51927"></a>160 <a class="indexterm" name="id3 51934"></a>161 <a class="indexterm" name="id3 51941"></a>162 <a class="indexterm" name="id3 51948"></a>158 <a class="indexterm" name="id374985"></a> 159 <a class="indexterm" name="id374992"></a> 160 <a class="indexterm" name="id374999"></a> 161 <a class="indexterm" name="id375006"></a> 163 162 In addition to differently encrypted passwords, Windows also stores certain data for each 164 163 user that is not stored in a UNIX user database: for example, workstations the user may logon from, 165 164 the location where the user's profile is stored, and so on. Samba retrieves and stores this 166 information using a <a class=" indexterm" name="id351957"></a>passdb backend. Commonly available backends are LDAP,167 tdbsam, and plain text file. For more information, see the man page for <code class="filename">smb.conf</code> regarding the 168 <a class=" indexterm" name="id351971"></a>passdb backendparameter.165 information using a <a class="link" href="smb.conf.5.html#PASSDBBACKEND">passdb backend</a>. Commonly available backends are LDAP, 166 tdbsam, and plain text file. For more information, see the man page for <code class="filename">smb.conf</code> regarding the 167 <a class="link" href="smb.conf.5.html#PASSDBBACKEND">passdb backend</a> parameter. 169 168 </p><div class="figure"><a name="idmap-sid2uid"></a><p class="title"><b>Figure 11.1. IDMAP: Resolution of SIDs to UIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-sid2uid.png" width="216" alt="IDMAP: Resolution of SIDs to UIDs."></div></div></div><br class="figure-break"><p> 170 <a class="indexterm" name="id3 52022"></a>171 <a class="indexterm" name="id3 52029"></a>172 <a class="indexterm" name="id3 52036"></a>169 <a class="indexterm" name="id375087"></a> 170 <a class="indexterm" name="id375094"></a> 171 <a class="indexterm" name="id375100"></a> 173 172 The resolution of SIDs to UIDs is fundamental to correct operation of Samba. In both cases shown, if winbindd 174 is not running or cannot be contacted, then only local SID/UID resolution is possible. See <a href="passdb.html#idmap-sid2uid" title="Figure 11.1. IDMAP: Resolution of SIDs to UIDs.">resolution of SIDs to UIDs</a> and <ahref="passdb.html#idmap-uid2sid" title="Figure 11.2. IDMAP: Resolution of UIDs to SIDs.">resolution of UIDs173 is not running or cannot be contacted, then only local SID/UID resolution is possible. See <a class="link" href="passdb.html#idmap-sid2uid" title="Figure 11.1. IDMAP: Resolution of SIDs to UIDs.">resolution of SIDs to UIDs</a> and <a class="link" href="passdb.html#idmap-uid2sid" title="Figure 11.2. IDMAP: Resolution of UIDs to SIDs.">resolution of UIDs 175 174 to SIDs</a> diagrams. 176 </p><div class="figure"><a name="idmap-uid2sid"></a><p class="title"><b>Figure 11.2. IDMAP: Resolution of UIDs to SIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-uid2sid.png" width="270" alt="IDMAP: Resolution of UIDs to SIDs."></div></div></div><br class="figure-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 52102"></a>Important Notes About Security</h3></div></div></div><p>177 <a class="indexterm" name="id3 52110"></a>178 <a class="indexterm" name="id3 52117"></a>179 <a class="indexterm" name="id3 52124"></a>180 <a class="indexterm" name="id3 52131"></a>181 <a class="indexterm" name="id3 52137"></a>175 </p><div class="figure"><a name="idmap-uid2sid"></a><p class="title"><b>Figure 11.2. IDMAP: Resolution of UIDs to SIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-uid2sid.png" width="270" alt="IDMAP: Resolution of UIDs to SIDs."></div></div></div><br class="figure-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id375167"></a>Important Notes About Security</h3></div></div></div><p> 176 <a class="indexterm" name="id375175"></a> 177 <a class="indexterm" name="id375182"></a> 178 <a class="indexterm" name="id375188"></a> 179 <a class="indexterm" name="id375195"></a> 180 <a class="indexterm" name="id375202"></a> 182 181 The UNIX and SMB password encryption techniques seem similar on the surface. This 183 182 similarity is, however, only skin deep. The UNIX scheme typically sends clear-text 184 183 passwords over the network when logging in. This is bad. The SMB encryption scheme 185 never sends the clear-text password over the network, but it does store the 16-byte 184 never sends the clear-text password over the network, but it does store the 16-byte 186 185 hashed values on disk. This is also bad. Why? Because the 16 byte hashed values 187 186 are a “<span class="quote">password equivalent.</span>” You cannot derive the user's password from them, but … … 193 192 be protected accordingly. 194 193 </p><p> 195 <a class="indexterm" name="id3 52159"></a>196 <a class="indexterm" name="id3 52166"></a>197 <a class="indexterm" name="id3 52172"></a>194 <a class="indexterm" name="id375224"></a> 195 <a class="indexterm" name="id375230"></a> 196 <a class="indexterm" name="id375237"></a> 198 197 Ideally, we would like a password scheme that involves neither plaintext passwords 199 198 on the network nor plaintext passwords on disk. Unfortunately, this is not available because Samba is stuck with 200 199 having to be compatible with other SMB systems (Windows NT, Windows for Workgroups, Windows 9x/Me). 201 200 </p><p> 202 <a class="indexterm" name="id3 52185"></a>203 <a class="indexterm" name="id3 52192"></a>201 <a class="indexterm" name="id375250"></a> 202 <a class="indexterm" name="id375257"></a> 204 203 Windows NT 4.0 Service Pack 3 changed the default setting so plaintext passwords 205 204 are disabled from being sent over the wire. This mandates either the use of encrypted 206 205 password support or editing the Windows NT registry to re-enable plaintext passwords. 207 206 </p><p> 208 <a class="indexterm" name="id3 52204"></a>209 <a class="indexterm" name="id3 52211"></a>207 <a class="indexterm" name="id375269"></a> 208 <a class="indexterm" name="id375276"></a> 210 209 The following versions of Microsoft Windows do not support full domain security protocols, 211 210 although they may log onto a domain environment: 212 211 </p><div class="itemizedlist"><ul type="disc"><li><p>MS DOS Network client 3.0 with the basic network redirector installed.</p></li><li><p>Windows 95 with the network redirector update installed.</p></li><li><p>Windows 98 [Second Edition].</p></li><li><p>Windows Me.</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 213 <a class="indexterm" name="id3 52247"></a>214 <a class="indexterm" name="id3 52254"></a>215 <a class="indexterm" name="id3 52260"></a>212 <a class="indexterm" name="id375311"></a> 213 <a class="indexterm" name="id375318"></a> 214 <a class="indexterm" name="id375325"></a> 216 215 MS Windows XP Home does not have facilities to become a domain member, and it cannot participate in domain logons. 217 216 </p></div><p> 218 217 The following versions of MS Windows fully support domain security protocols. 219 218 </p><div class="itemizedlist"><ul type="disc"><li><p>Windows NT 3.5x.</p></li><li><p>Windows NT 4.0.</p></li><li><p>Windows 2000 Professional.</p></li><li><p>Windows 200x Server/Advanced Server.</p></li><li><p>Windows XP Professional.</p></li></ul></div><p> 220 <a class="indexterm" name="id3 52303"></a>221 <a class="indexterm" name="id3 52310"></a>222 <a class="indexterm" name="id3 52316"></a>223 <a class="indexterm" name="id3 52323"></a>224 <a class="indexterm" name="id3 52330"></a>225 <a class="indexterm" name="id3 52337"></a>219 <a class="indexterm" name="id375368"></a> 220 <a class="indexterm" name="id375374"></a> 221 <a class="indexterm" name="id375381"></a> 222 <a class="indexterm" name="id375388"></a> 223 <a class="indexterm" name="id375395"></a> 224 <a class="indexterm" name="id375402"></a> 226 225 All current releases of Microsoft SMB/CIFS clients support authentication via the 227 226 SMB challenge/response mechanism described here. Enabling clear-text authentication … … 230 229 handling. 231 230 </p><p> 232 <a class="indexterm" name="id3 52350"></a>233 <a class="indexterm" name="id3 52357"></a>234 <a class="indexterm" name="id3 52364"></a>235 <a class="indexterm" name="id3 52371"></a>236 <a class="indexterm" name="id3 52377"></a>231 <a class="indexterm" name="id375415"></a> 232 <a class="indexterm" name="id375422"></a> 233 <a class="indexterm" name="id375428"></a> 234 <a class="indexterm" name="id375435"></a> 235 <a class="indexterm" name="id375442"></a> 237 236 MS Windows clients will cache the encrypted password alone. Where plaintext passwords 238 237 are re-enabled through the appropriate registry change, the plaintext password is never … … 241 240 effect an auto-reconnect. If the resource server does not support encrypted passwords, the 242 241 auto-reconnect will fail. Use of encrypted passwords is strongly advised. 243 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 52390"></a>Advantages of Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>244 <a class="indexterm" name="id3 52401"></a>245 <a class="indexterm" name="id3 52408"></a>246 <a class="indexterm" name="id3 52415"></a>242 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id375454"></a>Advantages of Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> 243 <a class="indexterm" name="id375466"></a> 244 <a class="indexterm" name="id375472"></a> 245 <a class="indexterm" name="id375479"></a> 247 246 Plaintext passwords are not passed across the network. Someone using a network sniffer 248 247 cannot just record passwords going to the SMB server. 249 248 </p></li><li><p> 250 <a class="indexterm" name="id3 52427"></a>251 <a class="indexterm" name="id3 52434"></a>252 <a class="indexterm" name="id3 52441"></a>249 <a class="indexterm" name="id375492"></a> 250 <a class="indexterm" name="id375499"></a> 251 <a class="indexterm" name="id375505"></a> 253 252 Plaintext passwords are not stored anywhere in memory or on disk. 254 253 </p></li><li><p> 255 <a class="indexterm" name="id3 52453"></a>256 <a class="indexterm" name="id3 52459"></a>257 <a class="indexterm" name="id3 52466"></a>258 <a class="indexterm" name="id3 52473"></a>254 <a class="indexterm" name="id375517"></a> 255 <a class="indexterm" name="id375524"></a> 256 <a class="indexterm" name="id375531"></a> 257 <a class="indexterm" name="id375538"></a> 259 258 Windows NT does not like talking to a server that does not support encrypted passwords. It will refuse to 260 259 browse the server if the server is also in user-level security mode. It will insist on prompting the user for … … 262 261 encryption. 263 262 </p></li><li><p> 264 <a class="indexterm" name="id3 52487"></a>265 <a class="indexterm" name="id3 52494"></a>263 <a class="indexterm" name="id375552"></a> 264 <a class="indexterm" name="id375559"></a> 266 265 Encrypted password support allows automatic share (resource) reconnects. 267 266 </p></li><li><p> 268 <a class="indexterm" name="id3 52506"></a>269 <a class="indexterm" name="id3 52512"></a>267 <a class="indexterm" name="id375570"></a> 268 <a class="indexterm" name="id375577"></a> 270 269 Encrypted passwords are essential for PDC/BDC operation. 271 </p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 52523"></a>Advantages of Non-Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>272 <a class="indexterm" name="id3 52534"></a>270 </p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id375587"></a>Advantages of Non-Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> 271 <a class="indexterm" name="id375598"></a> 273 272 Plaintext passwords are not kept on disk and are not cached in memory. 274 273 </p></li><li><p> 275 <a class="indexterm" name="id3 52546"></a>276 <a class="indexterm" name="id3 52552"></a>274 <a class="indexterm" name="id375610"></a> 275 <a class="indexterm" name="id375617"></a> 277 276 Plaintext passwords use the same password file as other UNIX services, such as Login and FTP. 278 277 </p></li><li><p> 279 <a class="indexterm" name="id3 52564"></a>280 <a class="indexterm" name="id3 52571"></a>278 <a class="indexterm" name="id375629"></a> 279 <a class="indexterm" name="id375636"></a> 281 280 Use of other services (such as Telnet and FTP) that send plaintext passwords over 282 281 the network makes sending them for SMB not such a big deal. 283 </p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 52583"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div></div><p>284 <a class="indexterm" name="id3 52591"></a>285 <a class="indexterm" name="id3 52598"></a>286 <a class="indexterm" name="id3 52604"></a>282 </p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id375648"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div></div><p> 283 <a class="indexterm" name="id375656"></a> 284 <a class="indexterm" name="id375662"></a> 285 <a class="indexterm" name="id375669"></a> 287 286 Every operation in UNIX/Linux requires a user identifier (UID), just as in 288 287 MS Windows NT4/200x this requires a security identifier (SID). Samba provides 289 288 two means for mapping an MS Windows user to a UNIX/Linux UID. 290 289 </p><p> 291 <a class="indexterm" name="id3 52616"></a>292 <a class="indexterm" name="id3 52623"></a>293 <a class="indexterm" name="id3 52630"></a>294 <a class="indexterm" name="id3 52636"></a>295 <a class="indexterm" name="id3 52643"></a>290 <a class="indexterm" name="id375681"></a> 291 <a class="indexterm" name="id375688"></a> 292 <a class="indexterm" name="id375694"></a> 293 <a class="indexterm" name="id375701"></a> 294 <a class="indexterm" name="id375708"></a> 296 295 First, all Samba SAM database accounts require a UNIX/Linux UID that the account will map to. As users are 297 added to the account information database, Samba will call the <a class=" indexterm" name="id352652"></a>add user script296 added to the account information database, Samba will call the <a class="link" href="smb.conf.5.html#ADDUSERSCRIPT">add user script</a> 298 297 interface to add the account to the Samba host OS. In essence all accounts in the local SAM require a local 299 298 user account. 300 299 </p><p> 301 <a class="indexterm" name="id3 52663"></a>302 <a class="indexterm" name="id3 52670"></a>303 <a class="indexterm" name="id3 52676"></a>304 <a class="indexterm" name="id3 52683"></a>305 <a class="indexterm" name="id3 52690"></a>306 <a class="indexterm" name="id3 52696"></a>307 <a class="indexterm" name="id3 52703"></a>300 <a class="indexterm" name="id375732"></a> 301 <a class="indexterm" name="id375738"></a> 302 <a class="indexterm" name="id375745"></a> 303 <a class="indexterm" name="id375752"></a> 304 <a class="indexterm" name="id375758"></a> 305 <a class="indexterm" name="id375765"></a> 306 <a class="indexterm" name="id375772"></a> 308 307 The second way to map Windows SID to UNIX UID is via the <span class="emphasis"><em>idmap uid</em></span> and 309 308 <span class="emphasis"><em>idmap gid</em></span> parameters in <code class="filename">smb.conf</code>. Please refer to the man page for information about … … 311 310 or a member of a foreign domain) SAM server. 312 311 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="idmapbackend"></a>Mapping Common UIDs/GIDs on Distributed Machines</h3></div></div></div><p> 313 <a class="indexterm" name="id3 52739"></a>314 <a class="indexterm" name="id3 52746"></a>315 <a class="indexterm" name="id3 52752"></a>316 <a class="indexterm" name="id3 52759"></a>317 <a class="indexterm" name="id3 52765"></a>318 <a class="indexterm" name="id3 52772"></a>312 <a class="indexterm" name="id375808"></a> 313 <a class="indexterm" name="id375814"></a> 314 <a class="indexterm" name="id375821"></a> 315 <a class="indexterm" name="id375827"></a> 316 <a class="indexterm" name="id375834"></a> 317 <a class="indexterm" name="id375840"></a> 319 318 Samba-3 has a special facility that makes it possible to maintain identical UIDs and GIDs 320 319 on all servers in a distributed network. A distributed network is one where there exists … … 323 322 users are copying files across UNIX/Linux systems using tools such as <code class="literal">rsync</code>. 324 323 </p><p> 325 <a class="indexterm" name="id3 52791"></a>326 <a class="indexterm" name="id3 52798"></a>327 <a class="indexterm" name="id3 52805"></a>328 <a class="indexterm" name="id3 52812"></a>329 <a class="indexterm" name="id3 52818"></a>330 <a class="indexterm" name="id3 52825"></a>331 <a class="indexterm" name="id3 52832"></a>332 <a class="indexterm" name="id3 52838"></a>324 <a class="indexterm" name="id375860"></a> 325 <a class="indexterm" name="id375867"></a> 326 <a class="indexterm" name="id375874"></a> 327 <a class="indexterm" name="id375880"></a> 328 <a class="indexterm" name="id375887"></a> 329 <a class="indexterm" name="id375893"></a> 330 <a class="indexterm" name="id375900"></a> 331 <a class="indexterm" name="id375907"></a> 333 332 The special facility is enabled using a parameter called <em class="parameter"><code>idmap backend</code></em>. 334 333 The default setting for this parameter is an empty string. Technically it is possible to use 335 334 an LDAP-based idmap backend for UIDs and GIDs, but it makes most sense when this is done for 336 335 network configurations that also use LDAP for the SAM backend. 337 <a href="passdb.html#idmapbackendexample" title="Example 11.1. Example Configuration with the LDAP idmap Backend">Example Configuration with the LDAP idmap Backend</a>336 <a class="link" href="passdb.html#idmapbackendexample" title="Example 11.1. Example Configuration with the LDAP idmap Backend">Example Configuration with the LDAP idmap Backend</a> 338 337 shows that configuration. 339 </p><a class="indexterm" name="id3 52863"></a><div class="example"><a name="idmapbackendexample"></a><p class="title"><b>Example 11.1. Example Configuration with the LDAP idmap Backend</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id352896"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap-server.quenya.org:636</code></em></td></tr><tr><td># Alternatively, this could be specified as:</td></tr><tr><td><a class="indexterm" name="id352912"></a><em class="parameter"><code>idmap backend = ldap:ldaps://ldap-server.quenya.org</code></em></td></tr></table></div></div><br class="example-break"><p>340 <a class="indexterm" name="id3 52928"></a>341 <a class="indexterm" name="id3 52935"></a>338 </p><a class="indexterm" name="id375932"></a><div class="example"><a name="idmapbackendexample"></a><p class="title"><b>Example 11.1. Example Configuration with the LDAP idmap Backend</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id375964"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap-server.quenya.org:636</code></em></td></tr><tr><td># Alternatively, this could be specified as:</td></tr><tr><td><a class="indexterm" name="id375980"></a><em class="parameter"><code>idmap backend = ldap:ldaps://ldap-server.quenya.org</code></em></td></tr></table></div></div><br class="example-break"><p> 339 <a class="indexterm" name="id375995"></a> 340 <a class="indexterm" name="id376001"></a> 342 341 A network administrator who wants to make significant use of LDAP backends will sooner or later be 343 exposed to the excellent work done by PADL Software. PADL <a href="http://www.padl.com" target="_top">http://www.padl.com</a> have342 exposed to the excellent work done by PADL Software. PADL <a class="ulink" href="http://www.padl.com" target="_top">http://www.padl.com</a> have 344 343 produced and released to open source an array of tools that might be of interest. These tools include: 345 344 </p><div class="itemizedlist"><ul type="disc"><li><p> 346 <a class="indexterm" name="id3 52956"></a>347 <a class="indexterm" name="id3 52963"></a>348 <a class="indexterm" name="id3 52970"></a>349 <a class="indexterm" name="id3 52976"></a>350 <a class="indexterm" name="id3 52983"></a>351 <a class="indexterm" name="id3 52990"></a>352 <a class="indexterm" name="id3 52996"></a>353 <a class="indexterm" name="id3 53003"></a>345 <a class="indexterm" name="id376023"></a> 346 <a class="indexterm" name="id376029"></a> 347 <a class="indexterm" name="id376036"></a> 348 <a class="indexterm" name="id376042"></a> 349 <a class="indexterm" name="id376049"></a> 350 <a class="indexterm" name="id376056"></a> 351 <a class="indexterm" name="id376063"></a> 352 <a class="indexterm" name="id376069"></a> 354 353 <span class="emphasis"><em>nss_ldap:</em></span> An LDAP name service switch (NSS) module to provide native 355 354 name service support for AIX, Linux, Solaris, and other operating systems. This tool 356 355 can be used for centralized storage and retrieval of UIDs and GIDs. 357 356 </p></li><li><p> 358 <a class="indexterm" name="id3 53021"></a>359 <a class="indexterm" name="id3 53028"></a>360 <a class="indexterm" name="id3 53035"></a>361 <a class="indexterm" name="id3 53042"></a>357 <a class="indexterm" name="id376088"></a> 358 <a class="indexterm" name="id376095"></a> 359 <a class="indexterm" name="id376101"></a> 360 <a class="indexterm" name="id376108"></a> 362 361 <span class="emphasis"><em>pam_ldap:</em></span> A PAM module that provides LDAP integration for UNIX/Linux 363 362 system access authentication. 364 363 </p></li><li><p> 365 <a class="indexterm" name="id3 53059"></a>366 <a class="indexterm" name="id3 53066"></a>367 <a class="indexterm" name="id3 53073"></a>368 <a class="indexterm" name="id3 53080"></a>364 <a class="indexterm" name="id376126"></a> 365 <a class="indexterm" name="id376132"></a> 366 <a class="indexterm" name="id376139"></a> 367 <a class="indexterm" name="id376146"></a> 369 368 <span class="emphasis"><em>idmap_ad:</em></span> An IDMAP backend that supports the Microsoft Services for 370 UNIX RFC 2307 schema available from the PADL Web 371 <a href="http://www.padl.com/download/xad_oss_plugins.tar.gz" target="_top">site</a>.372 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 53101"></a>Comments Regarding LDAP</h3></div></div></div><p>373 <a class="indexterm" name="id3 53109"></a>374 <a class="indexterm" name="id3 53118"></a>375 <a class="indexterm" name="id3 53125"></a>376 <a class="indexterm" name="id3 53132"></a>369 UNIX RFC 2307 schema available from the PADL Web 370 <a class="ulink" href="http://www.padl.com/download/xad_oss_plugins.tar.gz" target="_top">site</a>. 371 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id376168"></a>Comments Regarding LDAP</h3></div></div></div><p> 372 <a class="indexterm" name="id376176"></a> 373 <a class="indexterm" name="id376185"></a> 374 <a class="indexterm" name="id376192"></a> 375 <a class="indexterm" name="id376198"></a> 377 376 There is much excitement and interest in LDAP directories in the information technology world 378 377 today. The LDAP architecture was designed to be highly scalable. It was also designed for … … 381 380 Identity Management (FIM) solutions that can underlie a corporate Single Sign-On (SSO) environment. 382 381 </p><p> 383 <a class="indexterm" name="id3 53146"></a>384 <a class="indexterm" name="id3 53152"></a>385 <a class="indexterm" name="id3 53159"></a>386 <a class="indexterm" name="id3 53166"></a>382 <a class="indexterm" name="id376212"></a> 383 <a class="indexterm" name="id376219"></a> 384 <a class="indexterm" name="id376226"></a> 385 <a class="indexterm" name="id376232"></a> 387 386 LDAP implementations have been built across a wide variety of platforms. It lies at the core of Microsoft 388 387 Windows Active Directory services (ADS), Novell's eDirectory, as well as many others. Implementation of the … … 390 389 depend on some form of authentication services. 391 390 </p><p> 392 <a class="indexterm" name="id3 53179"></a>393 <a class="indexterm" name="id3 53186"></a>394 <a class="indexterm" name="id3 53193"></a>395 <a class="indexterm" name="id3 53199"></a>396 <a class="indexterm" name="id3 53206"></a>397 <a class="indexterm" name="id3 53213"></a>398 <a class="indexterm" name="id3 53220"></a>399 <a class="indexterm" name="id3 53227"></a>400 <a class="indexterm" name="id3 53233"></a>401 <a class="indexterm" name="id3 53240"></a>402 <a class="indexterm" name="id3 53247"></a>403 <a class="indexterm" name="id3 53254"></a>404 <a class="indexterm" name="id3 53261"></a>405 <a class="indexterm" name="id3 53267"></a>391 <a class="indexterm" name="id376245"></a> 392 <a class="indexterm" name="id376252"></a> 393 <a class="indexterm" name="id376259"></a> 394 <a class="indexterm" name="id376266"></a> 395 <a class="indexterm" name="id376273"></a> 396 <a class="indexterm" name="id376279"></a> 397 <a class="indexterm" name="id376286"></a> 398 <a class="indexterm" name="id376293"></a> 399 <a class="indexterm" name="id376300"></a> 400 <a class="indexterm" name="id376307"></a> 401 <a class="indexterm" name="id376313"></a> 402 <a class="indexterm" name="id376320"></a> 403 <a class="indexterm" name="id376327"></a> 404 <a class="indexterm" name="id376334"></a> 406 405 UNIX services can utilize LDAP directory information for authentication and access controls 407 406 through intermediate tools and utilities. The total environment that consists of the LDAP directory 408 407 and the middle-ware tools and utilities makes it possible for all user access to the UNIX platform 409 408 to be managed from a central environment and yet distributed to wherever the point of need may 410 be physically located. Applications that benefit from this infrastructure include: UNIX login 409 be physically located. Applications that benefit from this infrastructure include: UNIX login 411 410 shells, mail and messaging systems, quota controls, printing systems, DNS servers, DHCP servers, 412 411 and also Samba. 413 412 </p><p> 414 <a class="indexterm" name="id3 53288"></a>415 <a class="indexterm" name="id3 53294"></a>416 <a class="indexterm" name="id3 53301"></a>417 <a class="indexterm" name="id3 53308"></a>418 <a class="indexterm" name="id3 53315"></a>419 <a class="indexterm" name="id3 53322"></a>413 <a class="indexterm" name="id376349"></a> 414 <a class="indexterm" name="id376356"></a> 415 <a class="indexterm" name="id376363"></a> 416 <a class="indexterm" name="id376369"></a> 417 <a class="indexterm" name="id376376"></a> 418 <a class="indexterm" name="id376383"></a> 420 419 Many sites are installing LDAP for the first time in order to provide a scalable passdb backend 421 420 for Samba. Others are faced with the need to adapt an existing LDAP directory to new uses such … … 425 424 information systems management costs. 426 425 </p><p> 427 <a class="indexterm" name="id3 53336"></a>428 <a class="indexterm" name="id3 53343"></a>426 <a class="indexterm" name="id376398"></a> 427 <a class="indexterm" name="id376404"></a> 429 428 Do not rush into an LDAP deployment. Take the time to understand how the design of the Directory 430 429 Information Tree (DIT) may impact current and future site needs, as well as the ability to meet 431 430 them. The way that Samba SAM information should be stored within the DIT varies from site to site 432 431 and with each implementation new experience is gained. It is well understood by LDAP veterans that 433 first implementations create awakening, second implementations of LDAP create fear, and 432 first implementations create awakening, second implementations of LDAP create fear, and 434 433 third-generation deployments bring peace and tranquility. 435 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 53358"></a>Caution Regarding LDAP and Samba</h4></div></div></div><p>436 <a class="indexterm" name="id3 53366"></a>437 <a class="indexterm" name="id3 53372"></a>438 <a class="indexterm" name="id3 53379"></a>439 <a class="indexterm" name="id3 53386"></a>440 <a class="indexterm" name="id3 53393"></a>441 <a class="indexterm" name="id3 53400"></a>442 <a class="indexterm" name="id3 53406"></a>434 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id376419"></a>Caution Regarding LDAP and Samba</h4></div></div></div><p> 435 <a class="indexterm" name="id376427"></a> 436 <a class="indexterm" name="id376434"></a> 437 <a class="indexterm" name="id376441"></a> 438 <a class="indexterm" name="id376447"></a> 439 <a class="indexterm" name="id376454"></a> 440 <a class="indexterm" name="id376461"></a> 441 <a class="indexterm" name="id376468"></a> 443 442 Samba requires UNIX POSIX identity information as well as a place to store information that is 444 443 specific to Samba and the Windows networking environment. The most used information that must … … 446 445 trust accounts, and intermediate information specific to Samba internals. 447 446 </p><p> 448 <a class="indexterm" name="id3 53420"></a>449 <a class="indexterm" name="id3 53427"></a>450 <a class="indexterm" name="id3 53433"></a>447 <a class="indexterm" name="id376481"></a> 448 <a class="indexterm" name="id376488"></a> 449 <a class="indexterm" name="id376495"></a> 451 450 The example deployment guidelines in this book, as well as other books and HOWTO documents 452 451 available from the internet may not fit with established directory designs and implementations. … … 455 454 the LDAP directory for use with Samba may not suit your needs. 456 455 </p><p> 457 <a class="indexterm" name="id3 53447"></a>456 <a class="indexterm" name="id376512"></a> 458 457 It is not uncommon, for sites that have existing LDAP DITs to find necessity to generate a 459 458 set of site-specific scripts and utilities to make it possible to deploy Samba within the … … 463 462 into deployment. 464 463 </p><p> 465 <a class="indexterm" name="id3 53465"></a>466 <a class="indexterm" name="id3 53472"></a>464 <a class="indexterm" name="id376527"></a> 465 <a class="indexterm" name="id376533"></a> 467 466 Above all, do not blindly use scripts and tools that are not suitable for your site. Check 468 467 and validate all scripts before you execute them to make sure that the existing infrastructure 469 468 will not be damaged by inadvertent use of an inappropriate tool. 470 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 53484"></a>LDAP Directories and Windows Computer Accounts</h3></div></div></div><p>471 <a class="indexterm" name="id3 53492"></a>472 <a class="indexterm" name="id3 53499"></a>473 <a class="indexterm" name="id3 53506"></a>469 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id376546"></a>LDAP Directories and Windows Computer Accounts</h3></div></div></div><p> 470 <a class="indexterm" name="id376554"></a> 471 <a class="indexterm" name="id376560"></a> 472 <a class="indexterm" name="id376567"></a> 474 473 Samba doesn't provide a turnkey solution to LDAP. It is best to deal with the design and 475 474 configuration of an LDAP directory prior to integration with Samba. A working knowledge … … 477 476 it a frustrating experience. 478 477 </p><p> 479 <a class="indexterm" name="id3 53519"></a>480 <a class="indexterm" name="id3 53526"></a>481 <a class="indexterm" name="id3 53532"></a>478 <a class="indexterm" name="id376580"></a> 479 <a class="indexterm" name="id376587"></a> 480 <a class="indexterm" name="id376594"></a> 482 481 Computer (machine) accounts can be placed wherever you like in an LDAP directory subject 483 482 to some constraints that are described in this chapter. 484 483 </p><p> 485 <a class="indexterm" name="id3 53544"></a>486 <a class="indexterm" name="id3 53551"></a>487 <a class="indexterm" name="id3 53557"></a>488 <a class="indexterm" name="id3 53564"></a>489 <a class="indexterm" name="id3 53571"></a>490 <a class="indexterm" name="id3 53578"></a>491 <a class="indexterm" name="id3 53585"></a>484 <a class="indexterm" name="id376605"></a> 485 <a class="indexterm" name="id376612"></a> 486 <a class="indexterm" name="id376619"></a> 487 <a class="indexterm" name="id376625"></a> 488 <a class="indexterm" name="id376632"></a> 489 <a class="indexterm" name="id376639"></a> 490 <a class="indexterm" name="id376646"></a> 492 491 The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba. 493 492 Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats … … 495 494 the machine account ends in a $ character, as do trust accounts. 496 495 </p><p> 497 <a class="indexterm" name="id3 53598"></a>498 <a class="indexterm" name="id3 53604"></a>499 <a class="indexterm" name="id3 53611"></a>500 <a class="indexterm" name="id3 53618"></a>501 <a class="indexterm" name="id3 53625"></a>496 <a class="indexterm" name="id376659"></a> 497 <a class="indexterm" name="id376666"></a> 498 <a class="indexterm" name="id376672"></a> 499 <a class="indexterm" name="id376679"></a> 500 <a class="indexterm" name="id376686"></a> 502 501 The need for Windows user, group, machine, trust, and other accounts to be tied to a valid UNIX 503 502 UID is a design decision that was made a long way back in the history of Samba development. It … … 505 504 Samba-3.x series. 506 505 </p><p> 507 <a class="indexterm" name="id3 53637"></a>508 <a class="indexterm" name="id3 53644"></a>509 <a class="indexterm" name="id3 53650"></a>506 <a class="indexterm" name="id376699"></a> 507 <a class="indexterm" name="id376705"></a> 508 <a class="indexterm" name="id376712"></a> 510 509 The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that 511 510 must refer back to the host operating system on which Samba is running. The NSS is the preferred … … 513 512 host OS it runs on. 514 513 </p><p> 515 <a class="indexterm" name="id3 53663"></a>516 <a class="indexterm" name="id3 53670"></a>517 <a class="indexterm" name="id3 53676"></a>518 <a class="indexterm" name="id3 53683"></a>519 <a class="indexterm" name="id3 53690"></a>520 <a class="indexterm" name="id3 53696"></a>521 <a class="indexterm" name="id3 53703"></a>514 <a class="indexterm" name="id376724"></a> 515 <a class="indexterm" name="id376731"></a> 516 <a class="indexterm" name="id376738"></a> 517 <a class="indexterm" name="id376744"></a> 518 <a class="indexterm" name="id376751"></a> 519 <a class="indexterm" name="id376758"></a> 520 <a class="indexterm" name="id376764"></a> 522 521 Samba asks the host OS to provide a UID via the “<span class="quote">passwd</span>”, “<span class="quote">shadow</span>”, 523 522 and “<span class="quote">group</span>” facilities in the NSS control (configuration) file. The best tool … … 527 526 all account entities can be located in an LDAP directory. 528 527 </p><p> 529 <a class="indexterm" name="id3 53728"></a>530 <a class="indexterm" name="id3 53735"></a>531 <a class="indexterm" name="id3 53742"></a>532 <a class="indexterm" name="id3 53748"></a>533 <a class="indexterm" name="id3 53755"></a>528 <a class="indexterm" name="id376789"></a> 529 <a class="indexterm" name="id376796"></a> 530 <a class="indexterm" name="id376803"></a> 531 <a class="indexterm" name="id376809"></a> 532 <a class="indexterm" name="id376816"></a> 534 533 For many the weapon of choice is to use the PADL nss_ldap utility. This utility must 535 534 be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That … … 538 537 of an LDAP directory is a complex subject that is beyond the scope of this documentation. 539 538 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="acctmgmttools"></a>Account Management Tools</h2></div></div></div><p> 540 <a class="indexterm" name="id3 53781"></a>541 <a class="indexterm" name="id3 53787"></a>542 <a class="indexterm" name="id3 53794"></a>539 <a class="indexterm" name="id376842"></a> 540 <a class="indexterm" name="id376848"></a> 541 <a class="indexterm" name="id376855"></a> 543 542 Samba provides two tools for management of user and machine accounts: 544 <code class="literal">smbpasswd</code> and <code class="literal">pdbedit</code>. 543 <code class="literal">smbpasswd</code> and <code class="literal">pdbedit</code>. 545 544 </p><p> 546 <a class="indexterm" name="id3 53816"></a>547 <a class="indexterm" name="id3 53823"></a>548 <a class="indexterm" name="id3 53830"></a>545 <a class="indexterm" name="id376878"></a> 546 <a class="indexterm" name="id376884"></a> 547 <a class="indexterm" name="id376891"></a> 549 548 The <code class="literal">pdbedit</code> can be used to manage account policies in addition to 550 549 Samba user account information. The policy management capability is used to administer … … 552 551 attempts. 553 552 </p><p> 554 <a class="indexterm" name="id3 53848"></a>555 <a class="indexterm" name="id3 53855"></a>556 <a class="indexterm" name="id3 53862"></a>557 <a class="indexterm" name="id3 53869"></a>553 <a class="indexterm" name="id376909"></a> 554 <a class="indexterm" name="id376916"></a> 555 <a class="indexterm" name="id376923"></a> 556 <a class="indexterm" name="id376930"></a> 558 557 Some people are confused when reference is made to <code class="literal">smbpasswd</code> because the 559 558 name refers to a storage mechanism for SambaSAMAccount information, but it is also the name 560 559 of a utility tool. That tool is destined to eventually be replaced by new functionality that 561 is being added to the <code class="literal">net</code> toolset (see <a href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command">the Net Command</a>.562 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 53897"></a>The <code class="literal">smbpasswd</code> Tool</h3></div></div></div><p>563 <a class="indexterm" name="id3 53911"></a>564 <a class="indexterm" name="id3 53917"></a>565 <a class="indexterm" name="id3 53924"></a>566 <a class="indexterm" name="id3 53931"></a>567 <a class="indexterm" name="id3 53938"></a>560 is being added to the <code class="literal">net</code> toolset (see <a class="link" href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command">the Net Command</a>. 561 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id376958"></a>The <code class="literal">smbpasswd</code> Tool</h3></div></div></div><p> 562 <a class="indexterm" name="id376972"></a> 563 <a class="indexterm" name="id376979"></a> 564 <a class="indexterm" name="id376985"></a> 565 <a class="indexterm" name="id376992"></a> 566 <a class="indexterm" name="id376999"></a> 568 567 The <code class="literal">smbpasswd</code> utility is similar to the <code class="literal">passwd</code> 569 568 and <code class="literal">yppasswd</code> programs. It maintains the two 32 byte password … … 572 571 backend</code></em> in the <code class="filename">smb.conf</code> file. 573 572 </p><p> 574 <a class="indexterm" name="id3 53980"></a>575 <a class="indexterm" name="id3 53986"></a>573 <a class="indexterm" name="id377041"></a> 574 <a class="indexterm" name="id377048"></a> 576 575 <code class="literal">smbpasswd</code> works in a client-server mode where it contacts the 577 576 local smbd to change the user's password on its behalf. This has enormous benefits. 578 577 </p><p> 579 <a class="indexterm" name="id3 54004"></a>580 <a class="indexterm" name="id3 54010"></a>578 <a class="indexterm" name="id377065"></a> 579 <a class="indexterm" name="id377072"></a> 581 580 <code class="literal">smbpasswd</code> has the capability to change passwords on Windows NT 582 581 servers (this only works when the request is sent to the NT PDC if changing an NT 583 582 domain user's password). 584 583 </p><p> 585 <a class="indexterm" name="id3 54028"></a>586 <a class="indexterm" name="id3 54034"></a>584 <a class="indexterm" name="id377089"></a> 585 <a class="indexterm" name="id377096"></a> 587 586 <code class="literal">smbpasswd</code> can be used to: 588 587 </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>add</em></span> user or machine accounts.</p></li><li><p><span class="emphasis"><em>delete</em></span> user or machine accounts.</p></li><li><p><span class="emphasis"><em>enable</em></span> user or machine accounts.</p></li><li><p><span class="emphasis"><em>disable</em></span> user or machine accounts.</p></li><li><p><span class="emphasis"><em>set to NULL</em></span> user passwords.</p></li><li><p><span class="emphasis"><em>manage</em></span> interdomain trust accounts.</p></li></ul></div><p> … … 603 602 new values do not match each other, then the password will not be changed. 604 603 </p><p> 605 <a class="indexterm" name="id3 54170"></a>604 <a class="indexterm" name="id377231"></a> 606 605 When invoked by an ordinary user, the command will allow only the user to change his or her own 607 606 SMB password. 608 607 </p><p> 609 <a class="indexterm" name="id3 54181"></a>610 <a class="indexterm" name="id3 54188"></a>608 <a class="indexterm" name="id377242"></a> 609 <a class="indexterm" name="id377249"></a> 611 610 When run by root, <code class="literal">smbpasswd</code> may take an optional argument specifying 612 611 the username whose SMB password you wish to change. When run as root, <code class="literal">smbpasswd</code> 613 does not prompt for or check the old password value, thus allowing root to set passwords 612 does not prompt for or check the old password value, thus allowing root to set passwords 614 613 for users who have forgotten their passwords. 615 614 </p><p> 616 <a class="indexterm" name="id3 54212"></a>617 <a class="indexterm" name="id3 54218"></a>618 <a class="indexterm" name="id3 54225"></a>619 <a class="indexterm" name="id3 54232"></a>615 <a class="indexterm" name="id377273"></a> 616 <a class="indexterm" name="id377280"></a> 617 <a class="indexterm" name="id377286"></a> 618 <a class="indexterm" name="id377293"></a> 620 619 <code class="literal">smbpasswd</code> is designed to work in the way familiar to UNIX 621 620 users who use the <code class="literal">passwd</code> or <code class="literal">yppasswd</code> commands. … … 623 622 password change capabilities. 624 623 </p><p> 625 <a class="indexterm" name="id3 54261"></a>624 <a class="indexterm" name="id377323"></a> 626 625 For more details on using <code class="literal">smbpasswd</code>, refer to the man page (the 627 626 definitive reference). 628 627 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="pdbeditthing"></a>The <code class="literal">pdbedit</code> Tool</h3></div></div></div><p> 629 <a class="indexterm" name="id3 54295"></a>630 <a class="indexterm" name="id3 54302"></a>631 <a class="indexterm" name="id3 54308"></a>632 <a class="indexterm" name="id3 54315"></a>628 <a class="indexterm" name="id377356"></a> 629 <a class="indexterm" name="id377363"></a> 630 <a class="indexterm" name="id377370"></a> 631 <a class="indexterm" name="id377376"></a> 633 632 <code class="literal">pdbedit</code> is a tool that can be used only by root. It is used to 634 manage the passdb backend, as well as domain-wide account policy settings. <code class="literal">pdbedit</code> 633 manage the passdb backend, as well as domain-wide account policy settings. <code class="literal">pdbedit</code> 635 634 can be used to: 636 635 </p><div class="itemizedlist"><ul type="disc"><li><p>add, remove, or modify user accounts.</p></li><li><p>list user accounts.</p></li><li><p>migrate user accounts.</p></li><li><p>migrate group accounts.</p></li><li><p>manage account policies.</p></li><li><p>manage domain access policy settings.</p></li></ul></div><p> 637 <a class="indexterm" name="id3 54371"></a>636 <a class="indexterm" name="id377432"></a> 638 637 Under the terms of the Sarbanes-Oxley Act of 2002, American businesses and organizations are mandated to 639 638 implement a series of <code class="literal">internal controls</code> and procedures to communicate, store, … … 641 640 </p><div class="orderedlist"><ol type="1"><li><p>Who has access to information systems that store financial data.</p></li><li><p>How personal and financial information is treated among employees and business 642 641 partners.</p></li><li><p>How security vulnerabilities are managed.</p></li><li><p>Security and patch level maintenance for all information systems.</p></li><li><p>How information systems changes are documented and tracked.</p></li><li><p>How information access controls are implemented and managed.</p></li><li><p>Auditability of all information systems in respect of change and security.</p></li><li><p>Disciplinary procedures and controls to ensure privacy.</p></li></ol></div><p> 643 <a class="indexterm" name="id3 54437"></a>644 <a class="indexterm" name="id3 54444"></a>642 <a class="indexterm" name="id377498"></a> 643 <a class="indexterm" name="id377505"></a> 645 644 In short, the Sarbanes-Oxley Act of 2002 is an instrument that enforces accountability in respect of 646 645 business related information systems so as to ensure the compliance of all information systems that … … 648 647 accountabilities are being demanded around the world. 649 648 </p><p> 650 <a class="indexterm" name="id3 54457"></a>651 <a class="indexterm" name="id3 54464"></a>652 <a class="indexterm" name="id3 54470"></a>653 <a class="indexterm" name="id3 54477"></a>654 <a class="indexterm" name="id3 54484"></a>649 <a class="indexterm" name="id377518"></a> 650 <a class="indexterm" name="id377525"></a> 651 <a class="indexterm" name="id377532"></a> 652 <a class="indexterm" name="id377538"></a> 653 <a class="indexterm" name="id377545"></a> 655 654 The need to be familiar with the Samba tools and facilities that permit information systems operation 656 655 in compliance with government laws and regulations is clear to all. The <code class="literal">pdbedit</code> is … … 660 659 </p><p> 661 660 Domain global policy controls available in Windows NT4 compared with Samba 662 is shown in <a href="passdb.html#policycontrols" title="Table 11.1. NT4 Domain v's Samba Policy Controls">NT4 Domain v's Samba Policy Controls</a>.661 is shown in <a class="link" href="passdb.html#policycontrols" title="Table 11.1. NT4 Domain v's Samba Policy Controls">NT4 Domain v's Samba Policy Controls</a>. 663 662 </p><div class="table"><a name="policycontrols"></a><p class="title"><b>Table 11.1. NT4 Domain v's Samba Policy Controls</b></p><div class="table-contents"><table summary="NT4 Domain v's Samba Policy Controls" border="1"><colgroup><col align="left"><col align="left"><col align="center"><col align="center"><col align="center"></colgroup><thead><tr><th align="left"><p>NT4 policy Name</p></th><th align="left"><p>Samba Policy Name</p></th><th align="center"><p>NT4 Range</p></th><th align="center"><p>Samba Range</p></th><th align="center"><p>Samba Default</p></th></tr></thead><tbody><tr><td align="left"><p>Maximum Password Age</p></td><td align="left"><p>maximum password age</p></td><td align="center"><p>0 - 999 (days)</p></td><td align="center"><p>0 - 4294967295 (sec)</p></td><td align="center"><p>4294967295</p></td></tr><tr><td align="left"><p>Minimum Password Age</p></td><td align="left"><p>minimum password age</p></td><td align="center"><p>0 - 999 (days)</p></td><td align="center"><p>0 - 4294967295 (sec)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Mimimum Password Length</p></td><td align="left"><p>min password length</p></td><td align="center"><p>1 - 14 (Chars)</p></td><td align="center"><p>0 - 4294967295 (Chars)</p></td><td align="center"><p>5</p></td></tr><tr><td align="left"><p>Password Uniqueness</p></td><td align="left"><p>password history</p></td><td align="center"><p>0 - 23 (#)</p></td><td align="center"><p>0 - 4294967295 (#)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Account Lockout - Reset count after</p></td><td align="left"><p>reset count minutes</p></td><td align="center"><p>1 - 99998 (min)</p></td><td align="center"><p>0 - 4294967295 (min)</p></td><td align="center"><p>30</p></td></tr><tr><td align="left"><p>Lockout after bad logon attempts</p></td><td align="left"><p>bad lockout attempt</p></td><td align="center"><p>0 - 998 (#)</p></td><td align="center"><p>0 - 4294967295 (#)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>*** Not Known ***</p></td><td align="left"><p>disconnect time</p></td><td align="center"><p>TBA</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Lockout Duration</p></td><td align="left"><p>lockout duration</p></td><td align="center"><p>1 - 99998 (min)</p></td><td align="center"><p>0 - 4294967295 (min)</p></td><td align="center"><p>30</p></td></tr><tr><td align="left"><p>Users must log on in order to change password</p></td><td align="left"><p>user must logon to change password</p></td><td align="center"><p>0/1</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>*** Registry Setting ***</p></td><td align="left"><p>refuse machine password change</p></td><td align="center"><p>0/1</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr></tbody></table></div></div><br class="table-break"><p> 664 <a class="indexterm" name="id3 54852"></a>665 <a class="indexterm" name="id3 54859"></a>666 <a class="indexterm" name="id3 54866"></a>667 <a class="indexterm" name="id3 54873"></a>663 <a class="indexterm" name="id377913"></a> 664 <a class="indexterm" name="id377920"></a> 665 <a class="indexterm" name="id377927"></a> 666 <a class="indexterm" name="id377934"></a> 668 667 The <code class="literal">pdbedit</code> tool is the only one that can manage the account 669 668 security and policy settings. It is capable of all operations that smbpasswd can 670 669 do as well as a superset of them. 671 670 </p><p> 672 <a class="indexterm" name="id3 54890"></a>673 <a class="indexterm" name="id3 54897"></a>674 <a class="indexterm" name="id3 54904"></a>671 <a class="indexterm" name="id377951"></a> 672 <a class="indexterm" name="id377958"></a> 673 <a class="indexterm" name="id377965"></a> 675 674 One particularly important purpose of the <code class="literal">pdbedit</code> is to allow 676 the migration of account information from one passdb backend to another.677 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 54919"></a>User Account Management</h4></div></div></div><p>678 <a class="indexterm" name="id3 54927"></a>679 <a class="indexterm" name="id3 54933"></a>680 <a class="indexterm" name="id3 54940"></a>681 <a class="indexterm" name="id3 54947"></a>682 <a class="indexterm" name="id3 54954"></a>683 <a class="indexterm" name="id3 54961"></a>684 <a class="indexterm" name="id3 54967"></a>675 the import/export of account information from one passdb backend to another. 676 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id377980"></a>User Account Management</h4></div></div></div><p> 677 <a class="indexterm" name="id377988"></a> 678 <a class="indexterm" name="id377995"></a> 679 <a class="indexterm" name="id378001"></a> 680 <a class="indexterm" name="id378008"></a> 681 <a class="indexterm" name="id378015"></a> 682 <a class="indexterm" name="id378022"></a> 683 <a class="indexterm" name="id378029"></a> 685 684 The <code class="literal">pdbedit</code> tool, like the <code class="literal">smbpasswd</code> tool, requires 686 685 that a POSIX user account already exists in the UNIX/Linux system accounts database (backend). … … 692 691 make use of these interface scripts. 693 692 </p><p> 694 <a class="indexterm" name="id3 55006"></a>695 <a class="indexterm" name="id3 55013"></a>693 <a class="indexterm" name="id378067"></a> 694 <a class="indexterm" name="id378074"></a> 696 695 Before attempting to use the <code class="literal">pdbedit</code> tool to manage user and machine 697 696 accounts, make certain that a system (POSIX) account has already been created. 698 </p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id3 55028"></a>Listing User and Machine Accounts</h5></div></div></div><p>699 <a class="indexterm" name="id3 55036"></a>700 <a class="indexterm" name="id3 55043"></a>697 </p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id378089"></a>Listing User and Machine Accounts</h5></div></div></div><p> 698 <a class="indexterm" name="id378097"></a> 699 <a class="indexterm" name="id378104"></a> 701 700 The following is an example of the user account information that is stored in 702 701 a tdbsam password backend. This listing was produced by running: … … 725 724 </pre><p> 726 725 </p><p> 727 <a class="indexterm" name="id3 55083"></a>726 <a class="indexterm" name="id378138"></a> 728 727 Accounts can also be listed in the older <code class="literal">smbpasswd</code> format: 729 728 </p><pre class="screen"> … … 750 749 C610EFE9A385A3E8AA46ADFD576E6881:[W ]:LCT-40F07A4 751 750 </pre><p> 752 <a class="indexterm" name="id3 55122"></a>753 <a class="indexterm" name="id3 55128"></a>754 <a class="indexterm" name="id3 55135"></a>755 <a class="indexterm" name="id3 55142"></a>756 <a class="indexterm" name="id3 55148"></a>757 <a class="indexterm" name="id3 55155"></a>758 The account information that was returned by this command in order from left to right 751 <a class="indexterm" name="id378176"></a> 752 <a class="indexterm" name="id378183"></a> 753 <a class="indexterm" name="id378190"></a> 754 <a class="indexterm" name="id378196"></a> 755 <a class="indexterm" name="id378203"></a> 756 <a class="indexterm" name="id378210"></a> 757 The account information that was returned by this command in order from left to right 759 758 consists of the following colon separated data: 760 759 </p><div class="itemizedlist"><ul type="disc"><li><p>Login ID.</p></li><li><p>UNIX UID.</p></li><li><p>Microsoft LanManager password hash (password converted to upper-case then hashed.</p></li><li><p>Microsoft NT password hash (hash of the case-preserved password).</p></li><li><p>Samba SAM Account Flags.</p></li><li><p>The LCT data (password last change time).</p></li></ul></div><p> 761 <a class="indexterm" name="id3 55203"></a>762 <a class="indexterm" name="id3 55209"></a>760 <a class="indexterm" name="id378257"></a> 761 <a class="indexterm" name="id378264"></a> 763 762 The Account Flags parameters are documented in the <code class="literal">pdbedit</code> man page, and are 764 briefly documented in <a href="passdb.html#TOSHARG-acctflags" title="Account Flags Management">the Account Flags Management section</a>.765 </p><p> 766 <a class="indexterm" name="id3 55234"></a>763 briefly documented in <a class="link" href="passdb.html#TOSHARG-acctflags" title="Account Flags Management">the Account Flags Management section</a>. 764 </p><p> 765 <a class="indexterm" name="id378289"></a> 767 766 The LCT data consists of 8 hexadecimal characters representing the time since January 1, 1970, of 768 767 the time when the password was last changed. 769 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id3 55244"></a>Adding User Accounts</h5></div></div></div><p>770 <a class="indexterm" name="id3 55252"></a>771 <a class="indexterm" name="id3 55259"></a>772 <a class="indexterm" name="id3 55266"></a>773 <a class="indexterm" name="id3 55272"></a>774 <a class="indexterm" name="id3 55279"></a>768 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id378299"></a>Adding User Accounts</h5></div></div></div><p> 769 <a class="indexterm" name="id378307"></a> 770 <a class="indexterm" name="id378314"></a> 771 <a class="indexterm" name="id378320"></a> 772 <a class="indexterm" name="id378327"></a> 773 <a class="indexterm" name="id378334"></a> 775 774 The <code class="literal">pdbedit</code> can be used to add a user account to a standalone server 776 775 or to a domain. In the example shown here the account for the user <code class="literal">vlaan</code> … … 804 803 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 805 804 </pre><p> 806 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id3 55321"></a>Deleting Accounts</h5></div></div></div><p>807 <a class="indexterm" name="id3 55329"></a>808 <a class="indexterm" name="id3 55336"></a>809 <a class="indexterm" name="id3 55342"></a>810 <a class="indexterm" name="id3 55349"></a>805 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id378376"></a>Deleting Accounts</h5></div></div></div><p> 806 <a class="indexterm" name="id378384"></a> 807 <a class="indexterm" name="id378390"></a> 808 <a class="indexterm" name="id378397"></a> 809 <a class="indexterm" name="id378404"></a> 811 810 An account can be deleted from the SambaSAMAccount database 812 811 </p><pre class="screen"> … … 816 815 SambaSAMAccount (passdb backend) database, it is not removed from the UNIX account backend. 817 816 </p><p> 818 <a class="indexterm" name="id3 55373"></a>819 <a class="indexterm" name="id3 55380"></a>817 <a class="indexterm" name="id378428"></a> 818 <a class="indexterm" name="id378435"></a> 820 819 The use of the NT4 domain user manager to delete an account will trigger the <em class="parameter"><code>delete user 821 820 script</code></em>, but not the <code class="literal">pdbedit</code> tool. 822 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id3 55402"></a>Changing User Accounts</h5></div></div></div><p>823 <a class="indexterm" name="id3 55409"></a>821 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id378456"></a>Changing User Accounts</h5></div></div></div><p> 822 <a class="indexterm" name="id378464"></a> 824 823 Refer to the <code class="literal">pdbedit</code> man page for a full synopsis of all operations 825 824 that are available with this tool. 826 825 </p><p> 827 <a class="indexterm" name="id3 55426"></a>826 <a class="indexterm" name="id378481"></a> 828 827 An example of a simple change in the user account information is the change of the full name 829 828 information shown here: … … 837 836 </pre><p> 838 837 </p><p> 839 <a class="indexterm" name="id3 55450"></a>840 <a class="indexterm" name="id3 55457"></a>841 <a class="indexterm" name="id3 55464"></a>838 <a class="indexterm" name="id378505"></a> 839 <a class="indexterm" name="id378512"></a> 840 <a class="indexterm" name="id378519"></a> 842 841 Let us assume for a moment that a user's password has expired and the user is unable to 843 842 change the password at this time. It may be necessary to give the user additional grace time … … 854 853 ... 855 854 </pre><p> 856 <a class="indexterm" name="id3 55487"></a>857 <a class="indexterm" name="id3 55494"></a>855 <a class="indexterm" name="id378542"></a> 856 <a class="indexterm" name="id378549"></a> 858 857 The user has recorded 2 bad logon attempts and the next will lock the account, but the 859 858 password is also expired. Here is how this account can be reset: … … 887 886 ... 888 887 </pre><p> 889 <a class="indexterm" name="id3 55549"></a>890 <a class="indexterm" name="id3 55556"></a>888 <a class="indexterm" name="id378604"></a> 889 <a class="indexterm" name="id378611"></a> 891 890 Refer to the strptime man page for specific time format information. 892 891 </p><p> 893 <a class="indexterm" name="id3 55567"></a>894 <a class="indexterm" name="id3 55574"></a>892 <a class="indexterm" name="id378622"></a> 893 <a class="indexterm" name="id378628"></a> 895 894 Please refer to the pdbedit man page for further information relating to SambaSAMAccount 896 895 management. 897 896 </p><div class="sect5" lang="en"><div class="titlepage"><div><div><h6 class="title"><a name="TOSHARG-acctflags"></a>Account Flags Management</h6></div></div></div><p> 898 <a class="indexterm" name="id3 55594"></a>899 <a class="indexterm" name="id3 55600"></a>900 <a class="indexterm" name="id3 55609"></a>901 <a class="indexterm" name="id3 55616"></a>897 <a class="indexterm" name="id378648"></a> 898 <a class="indexterm" name="id378655"></a> 899 <a class="indexterm" name="id378664"></a> 900 <a class="indexterm" name="id378671"></a> 902 901 The Samba SAM account flags are properly called the ACB (account control block) within 903 the Samba source code. In some parts of the Samba source code they are referred to as the 902 the Samba source code. In some parts of the Samba source code they are referred to as the 904 903 account encode_bits, and also as the account control flags. 905 904 </p><p> 906 <a class="indexterm" name="id3 55628"></a>907 <a class="indexterm" name="id3 55635"></a>908 <a class="indexterm" name="id3 55642"></a>909 <a class="indexterm" name="id3 55649"></a>910 <a class="indexterm" name="id3 55655"></a>905 <a class="indexterm" name="id378683"></a> 906 <a class="indexterm" name="id378690"></a> 907 <a class="indexterm" name="id378696"></a> 908 <a class="indexterm" name="id378703"></a> 909 <a class="indexterm" name="id378710"></a> 911 910 The manual adjustment of user, machine (workstation or server) or an inter-domain trust 912 911 account account flgas should not be necessary under normal conditions of use of Samba. On the other hand, … … 914 913 useful. The tool of choice by which such correction can be affected is the <code class="literal">pdbedit</code> utility. 915 914 </p><p> 916 <a class="indexterm" name="id3 55675"></a>917 <a class="indexterm" name="id3 55682"></a>915 <a class="indexterm" name="id378729"></a> 916 <a class="indexterm" name="id378736"></a> 918 917 There have been a few requests for information regarding the account flags from developers 919 918 who are creating their own Samba management tools. An example of a need for information regarding … … 921 920 to manage an LDAP directory. 922 921 </p><p> 923 <a class="indexterm" name="id3 55694"></a>924 <a class="indexterm" name="id3 55701"></a>922 <a class="indexterm" name="id378749"></a> 923 <a class="indexterm" name="id378756"></a> 925 924 The account flag field can contain up to 16 characters. Presently, only 11 are in use. 926 These are listed in <a href="passdb.html#accountflags" title="Table 11.2. Samba SAM Account Control Block Flags">Samba SAM Account Control Block Flags</a>.925 These are listed in <a class="link" href="passdb.html#accountflags" title="Table 11.2. Samba SAM Account Control Block Flags">Samba SAM Account Control Block Flags</a>. 927 926 The order in which the flags are specified to the <code class="literal">pdbedit</code> command is not important. 928 927 In fact, they can be set without problem in any order in the SambaAcctFlags record in the LDAP directory. 929 928 </p><div class="table"><a name="accountflags"></a><p class="title"><b>Table 11.2. Samba SAM Account Control Block Flags</b></p><div class="table-contents"><table summary="Samba SAM Account Control Block Flags" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Flag</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">D</td><td align="left">Account is disabled.</td></tr><tr><td align="center">H</td><td align="left">A home directory is required.</td></tr><tr><td align="center">I</td><td align="left">An inter-domain trust account.</td></tr><tr><td align="center">L</td><td align="left">Account has been auto-locked.</td></tr><tr><td align="center">M</td><td align="left">An MNS (Microsoft network service) logon account.</td></tr><tr><td align="center">N</td><td align="left">Password not required.</td></tr><tr><td align="center">S</td><td align="left">A server trust account.</td></tr><tr><td align="center">T</td><td align="left">Temporary duplicate account entry.</td></tr><tr><td align="center">U</td><td align="left">A normal user account.</td></tr><tr><td align="center">W</td><td align="left">A workstation trust account.</td></tr><tr><td align="center">X</td><td align="left">Password does not expire.</td></tr></tbody></table></div></div><br class="table-break"><p> 930 <a class="indexterm" name="id3 55922"></a>931 <a class="indexterm" name="id3 55929"></a>929 <a class="indexterm" name="id378977"></a> 930 <a class="indexterm" name="id378984"></a> 932 931 An example of use of the <code class="literal">pdbedit</code> utility to set the account control flags 933 932 is shown here: 934 933 </p><pre class="screen"> 935 <code class="prompt">root# </code> pdbedit -r -c "[DLX]" j ra934 <code class="prompt">root# </code> pdbedit -r -c "[DLX]" jht 936 935 Unix username: jht 937 936 NT username: jht … … 957 956 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 958 957 </pre><p> 959 <a class="indexterm" name="id3 55961"></a>958 <a class="indexterm" name="id379016"></a> 960 959 The flags can be reset to the default settings by executing: 961 960 </p><pre class="screen"> 962 <code class="prompt">root# </code> pdbedit -r -c "[]" j ra961 <code class="prompt">root# </code> pdbedit -r -c "[]" jht 963 962 Unix username: jht 964 963 NT username: jht … … 984 983 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 985 984 </pre><p> 986 </p></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id3 55998"></a>Domain Account Policy Managment</h5></div></div></div><p>987 <a class="indexterm" name="id3 56006"></a>988 <a class="indexterm" name="id3 56012"></a>985 </p></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id379045"></a>Domain Account Policy Managment</h5></div></div></div><p> 986 <a class="indexterm" name="id379053"></a> 987 <a class="indexterm" name="id379060"></a> 989 988 To view the domain account access policies that may be configured execute: 990 989 </p><pre class="screen"> … … 1032 1031 Account policies must be set individually on each PDC and BDC. At this time (Samba 3.0.11 to Samba 3.0.14a) 1033 1032 account policies are not replicated automatically. This may be fixed before Samba 3.0.20 ships or some 1034 time there after. 1035 </p></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id356140"></a>Account Migration</h4></div></div></div><p> 1036 <a class="indexterm" name="id356148"></a> 1037 <a class="indexterm" name="id356155"></a> 1038 <a class="indexterm" name="id356162"></a> 1039 The <code class="literal">pdbedit</code> tool allows migration of authentication (account) 1040 databases from one backend to another. For example, to migrate accounts from an 1033 time there after. Please check the WHATSNEW.txt file in the Samba-3 tarball for specific update notiations 1034 regarding this facility. 1035 </p></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id379189"></a>Account Import/Export</h4></div></div></div><p> 1036 <a class="indexterm" name="id379196"></a> 1037 <a class="indexterm" name="id379203"></a> 1038 <a class="indexterm" name="id379210"></a> 1039 The <code class="literal">pdbedit</code> tool allows import/export of authentication (account) 1040 databases from one backend to another. For example, to import/export accounts from an 1041 1041 old <code class="filename">smbpasswd</code> database to a <em class="parameter"><code>tdbsam</code></em> 1042 1042 backend: 1043 1043 </p><div class="procedure"><ol type="1"><li><p> 1044 Set the <a class="indexterm" name="id356197"></a>passdb backend = tdbsam, smbpasswd. 1044 <a class="indexterm" name="id379245"></a> 1045 </p><pre class="screen"> 1046 <code class="prompt">root# </code><strong class="userinput"><code>pdbedit -i smbpasswd -e tdbsam</code></strong> 1047 </pre><p> 1045 1048 </p></li><li><p> 1046 <a class="indexterm" name="id356210"></a> 1047 Execute: 1048 </p><pre class="screen"> 1049 <code class="prompt">root# </code><strong class="userinput"><code>pdbedit -i smbpasswd -e tdbsam</code></strong> 1050 </pre><p> 1051 </p></li><li><p> 1052 <a class="indexterm" name="id356240"></a> 1053 Remove the <em class="parameter"><code>smbpasswd</code></em> from the passdb backend 1054 configuration in <code class="filename">smb.conf</code>. 1055 </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id356265"></a>Password Backends</h2></div></div></div><p> 1056 <a class="indexterm" name="id356272"></a> 1057 <a class="indexterm" name="id356279"></a> 1058 Samba offers the greatest flexibility in backend account database design of any SMB/CIFS server 1059 technology available today. The flexibility is immediately obvious as one begins to explore this 1060 capability. 1049 <a class="indexterm" name="id379274"></a> 1050 Replace the <em class="parameter"><code>smbpasswd</code></em> with <em class="parameter"><code>tdbsam</code></em> in the 1051 <em class="parameter"><code>passdb backend</code></em> configuration in <code class="filename">smb.conf</code>. 1052 </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id379310"></a>Password Backends</h2></div></div></div><p> 1053 <a class="indexterm" name="id379318"></a> 1054 <a class="indexterm" name="id379325"></a> 1055 Samba offers flexibility in backend account database design. The flexibility is immediately obvious as one 1056 begins to explore this capability. Recent changes to Samba (since 3.0.23) have removed the mulitple backend 1057 feature in order to simplify problems that broke some installations. This removal has made the internal 1058 operation of Samba-3 more consistent and predictable. 1061 1059 </p><p> 1062 <a class="indexterm" name="id356291"></a> 1063 <a class="indexterm" name="id356298"></a> 1064 It is possible to specify not only multiple password backends, but even multiple 1065 backends of the same type. For example, to use two different <code class="literal">tdbsam</code> databases: 1066 1067 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id356317"></a><em class="parameter"><code>passdb backend = tdbsam:/etc/samba/passdb.tdb tdbsam:/etc/samba/old-passdb.tdb</code></em></td></tr></table><p> 1068 1069 What is possible is not always sensible. Be careful to avoid complexity to the point that it 1070 may be said that the solution is “<span class="quote">too clever by half!</span>” 1071 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id356336"></a>Plaintext</h3></div></div></div><p> 1072 <a class="indexterm" name="id356344"></a> 1073 <a class="indexterm" name="id356351"></a> 1074 <a class="indexterm" name="id356358"></a> 1075 <a class="indexterm" name="id356364"></a> 1076 <a class="indexterm" name="id356371"></a> 1077 <a class="indexterm" name="id356378"></a> 1078 Older versions of Samba retrieved user information from the UNIX user database 1060 <a class="indexterm" name="id379338"></a> 1061 <a class="indexterm" name="id379345"></a> 1062 Beginning with Samba 3.0.23 it is no longer possible to specify use of mulitple passdb backends. Earlier 1063 versions of Samba-3 made it possible to specify multiple password backends, and even multiple 1064 backends of the same type. The multiple passdb backend capability caused many problems with name to SID and 1065 SID to name ID resolution. The Samba team wrestled with the challenges and decided that this feature needed 1066 to be removed. 1067 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id379357"></a>Plaintext</h3></div></div></div><p> 1068 <a class="indexterm" name="id379364"></a> 1069 <a class="indexterm" name="id379371"></a> 1070 <a class="indexterm" name="id379378"></a> 1071 <a class="indexterm" name="id379385"></a> 1072 <a class="indexterm" name="id379392"></a> 1073 <a class="indexterm" name="id379398"></a> 1074 Older versions of Samba retrieved user information from the UNIX user database 1079 1075 and eventually some other fields from the file <code class="filename">/etc/samba/smbpasswd</code> 1080 or <code class="filename">/etc/smbpasswd</code>. When password encryption is disabled, no 1076 or <code class="filename">/etc/smbpasswd</code>. When password encryption is disabled, no 1081 1077 SMB-specific data is stored at all. Instead, all operations are conducted via the way 1082 1078 that the Samba host OS will access its <code class="filename">/etc/passwd</code> database. 1083 1079 On most Linux systems, for example, all user and group resolution is done via PAM. 1084 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 56408"></a>smbpasswd: Encrypted Password Database</h3></div></div></div><p>1085 <a class="indexterm" name="id3 56416"></a>1086 <a class="indexterm" name="id3 56425"></a>1087 <a class="indexterm" name="id3 56432"></a>1088 <a class="indexterm" name="id3 56438"></a>1089 Traditionally, when configuring <a class=" indexterm" name="id356446"></a>encrypt passwords = yes1080 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id379428"></a>smbpasswd: Encrypted Password Database</h3></div></div></div><p> 1081 <a class="indexterm" name="id379436"></a> 1082 <a class="indexterm" name="id379445"></a> 1083 <a class="indexterm" name="id379452"></a> 1084 <a class="indexterm" name="id379459"></a> 1085 Traditionally, when configuring <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS">encrypt passwords = yes</a> 1090 1086 in Samba's <code class="filename">smb.conf</code> file, user account information such as username, LM/NT password hashes, 1091 1087 password change times, and account flags have been stored in the <code class="filename">smbpasswd(5)</code> … … 1093 1089 (counted in the thousands). 1094 1090 </p><div class="itemizedlist"><ul type="disc"><li><p> 1095 <a class="indexterm" name="id3 56473"></a>1091 <a class="indexterm" name="id379497"></a> 1096 1092 The first problem is that all lookups must be performed sequentially. Given that 1097 1093 there are approximately two lookups per domain logon (one during intial logon validation … … 1100 1096 such as that used in databases. 1101 1097 </p></li><li><p> 1102 <a class="indexterm" name="id3 56488"></a>1103 <a class="indexterm" name="id3 56495"></a>1104 <a class="indexterm" name="id3 56501"></a>1105 <a class="indexterm" name="id3 56508"></a>1106 <a class="indexterm" name="id3 56515"></a>1098 <a class="indexterm" name="id379512"></a> 1099 <a class="indexterm" name="id379518"></a> 1100 <a class="indexterm" name="id379525"></a> 1101 <a class="indexterm" name="id379532"></a> 1102 <a class="indexterm" name="id379538"></a> 1107 1103 The second problem is that administrators who desire to replicate an smbpasswd file 1108 1104 to more than one Samba server are left to use external tools such as … … 1110 1106 in-house scripts. 1111 1107 </p></li><li><p> 1112 <a class="indexterm" name="id3 56540"></a>1113 <a class="indexterm" name="id3 56546"></a>1114 <a class="indexterm" name="id3 56553"></a>1115 <a class="indexterm" name="id3 56560"></a>1116 <a class="indexterm" name="id3 56567"></a>1108 <a class="indexterm" name="id379563"></a> 1109 <a class="indexterm" name="id379570"></a> 1110 <a class="indexterm" name="id379577"></a> 1111 <a class="indexterm" name="id379584"></a> 1112 <a class="indexterm" name="id379590"></a> 1117 1113 Finally, the amount of information that is stored in an smbpasswd entry leaves 1118 1114 no room for additional attributes such as a home directory, password expiration time, 1119 1115 or even a relative identifier (RID). 1120 1116 </p></li></ul></div><p> 1121 <a class="indexterm" name="id3 56582"></a>1122 <a class="indexterm" name="id3 56589"></a>1123 <a class="indexterm" name="id3 56595"></a>1124 <a class="indexterm" name="id3 56602"></a>1117 <a class="indexterm" name="id379606"></a> 1118 <a class="indexterm" name="id379612"></a> 1119 <a class="indexterm" name="id379619"></a> 1120 <a class="indexterm" name="id379626"></a> 1125 1121 As a result of these deficiencies, a more robust means of storing user attributes 1126 1122 used by smbd was developed. The API that defines access to user accounts 1127 1123 is commonly referred to as the samdb interface (previously, this was called the passdb 1128 API and is still so named in the Samba source code trees). 1129 </p><p> 1130 <a class="indexterm" name="id3 56615"></a>1131 <a class="indexterm" name="id3 56622"></a>1132 <a class="indexterm" name="id3 56628"></a>1133 <a class="indexterm" name="id3 56635"></a>1134 <a class="indexterm" name="id3 56642"></a>1124 API and is still so named in the Samba source code trees). 1125 </p><p> 1126 <a class="indexterm" name="id379638"></a> 1127 <a class="indexterm" name="id379645"></a> 1128 <a class="indexterm" name="id379652"></a> 1129 <a class="indexterm" name="id379659"></a> 1130 <a class="indexterm" name="id379666"></a> 1135 1131 Samba provides an enhanced set of passdb backends that overcome the deficiencies 1136 1132 of the smbpasswd plaintext database. These are tdbsam and ldapsam. 1137 1133 Of these, ldapsam will be of most interest to large corporate or enterprise sites. 1138 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 56653"></a>tdbsam</h3></div></div></div><p>1139 <a class="indexterm" name="id3 56661"></a>1140 <a class="indexterm" name="id3 56670"></a>1141 <a class="indexterm" name="id3 56679"></a>1134 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id379677"></a>tdbsam</h3></div></div></div><p> 1135 <a class="indexterm" name="id379685"></a> 1136 <a class="indexterm" name="id379694"></a> 1137 <a class="indexterm" name="id379703"></a> 1142 1138 Samba can store user and machine account data in a “<span class="quote">TDB</span>” (trivial database). 1143 1139 Using this backend does not require any additional configuration. This backend is 1144 1140 recommended for new installations that do not require LDAP. 1145 1141 </p><p> 1146 <a class="indexterm" name="id3 56694"></a>1147 <a class="indexterm" name="id3 56701"></a>1148 <a class="indexterm" name="id3 56708"></a>1149 <a class="indexterm" name="id3 56714"></a>1142 <a class="indexterm" name="id379718"></a> 1143 <a class="indexterm" name="id379725"></a> 1144 <a class="indexterm" name="id379731"></a> 1145 <a class="indexterm" name="id379738"></a> 1150 1146 As a general guide, the Samba Team does not recommend using the tdbsam backend for sites 1151 1147 that have 250 or more users. Additionally, tdbsam is not capable of scaling for use … … 1153 1149 database. Clearly, for reason of scalability, the use of ldapsam should be encouraged. 1154 1150 </p><p> 1155 <a class="indexterm" name="id3 56727"></a>1156 <a class="indexterm" name="id3 56734"></a>1157 <a class="indexterm" name="id3 56741"></a>1151 <a class="indexterm" name="id379751"></a> 1152 <a class="indexterm" name="id379758"></a> 1153 <a class="indexterm" name="id379765"></a> 1158 1154 The recommendation of a 250-user limit is purely based on the notion that this 1159 1155 would generally involve a site that has routed networks, possibly spread across … … 1161 1157 the performance-based scalability limits of the tdbsam architecture. 1162 1158 </p><p> 1163 <a class="indexterm" name="id3 56754"></a>1164 <a class="indexterm" name="id3 56760"></a>1165 <a class="indexterm" name="id3 56767"></a>1166 <a class="indexterm" name="id3 56774"></a>1159 <a class="indexterm" name="id379777"></a> 1160 <a class="indexterm" name="id379784"></a> 1161 <a class="indexterm" name="id379791"></a> 1162 <a class="indexterm" name="id379798"></a> 1167 1163 There are sites that have thousands of users and yet require only one server. 1168 1164 One site recently reported having 4,500 user accounts on one UNIX system and … … 1172 1168 only on the need for a reliable distribution mechanism for the SambaSAMAccount 1173 1169 backend. 1174 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id3 56799"></a>ldapsam</h3></div></div></div><p>1175 <a class="indexterm" name="id3 56806"></a>1176 <a class="indexterm" name="id3 56813"></a>1177 <a class="indexterm" name="id3 56820"></a>1170 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id379822"></a>ldapsam</h3></div></div></div><p> 1171 <a class="indexterm" name="id379830"></a> 1172 <a class="indexterm" name="id379837"></a> 1173 <a class="indexterm" name="id379844"></a> 1178 1174 There are a few points to stress that the ldapsam does not provide. The LDAP 1179 1175 support referred to in this documentation does not include: 1180 1176 </p><div class="itemizedlist"><ul type="disc"><li><p>A means of retrieving user account information from 1181 1177 a Windows 200x Active Directory server.</p></li><li><p>A means of replacing /etc/passwd.</p></li></ul></div><p> 1182 <a class="indexterm" name="id3 56847"></a>1183 <a class="indexterm" name="id3 56854"></a>1184 <a class="indexterm" name="id3 56860"></a>1185 <a class="indexterm" name="id3 56867"></a>1178 <a class="indexterm" name="id379871"></a> 1179 <a class="indexterm" name="id379877"></a> 1180 <a class="indexterm" name="id379884"></a> 1181 <a class="indexterm" name="id379890"></a> 1186 1182 The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be 1187 obtained from <a href="http://www.padl.com/" target="_top">PADL Software</a>. More information about the1188 configuration of these packages may be found in <a href="http://safari.oreilly.com/?XmlId=1-56592-491-6" target="_top">1183 obtained from <a class="ulink" href="http://www.padl.com/" target="_top">PADL Software</a>. More information about the 1184 configuration of these packages may be found in <a class="ulink" href="http://safari.oreilly.com/?XmlId=1-56592-491-6" target="_top"> 1189 1185 <span class="emphasis"><em>LDAP, System Administration</em></span> by Gerald Carter, Chapter 6, Replacing NIS"</a>. 1190 1186 </p><p> 1191 <a class="indexterm" name="id3 56895"></a>1192 <a class="indexterm" name="id3 56901"></a>1193 <a class="indexterm" name="id3 56908"></a>1187 <a class="indexterm" name="id379918"></a> 1188 <a class="indexterm" name="id379925"></a> 1189 <a class="indexterm" name="id379932"></a> 1194 1190 This document describes how to use an LDAP directory for storing Samba user 1195 1191 account information traditionally stored in the smbpasswd(5) file. It is … … 1197 1193 and has a working directory server already installed. For more information 1198 1194 on LDAP architectures and directories, please refer to the following sites: 1199 </p><div class="itemizedlist"><ul type="disc"><li><p><a href="http://www.openldap.org/" target="_top">OpenLDAP</a></p></li><li><p><ahref="http://www.sun.com/software/products/directory_srvr_ee/index.xml" target="_top">1200 Sun One Directory Server</a></p></li><li><p><a href="http://www.novell.com/products/edirectory/" target="_top">Novell eDirectory</a></p></li><li><p><ahref="http://www-306.ibm.com/software/tivoli/products/directory-server/" target="_top">IBM1201 Tivoli Directory Server</a></p></li><li><p><a href="http://www.redhat.com/software/rha/directory/" target="_top">Red Hat Directory1202 Server</a></p></li><li><p><a href="http://www.linuxsecurity.com/content/view/119229" target="_top">Fedora Directory1195 </p><div class="itemizedlist"><ul type="disc"><li><p><a class="ulink" href="http://www.openldap.org/" target="_top">OpenLDAP</a></p></li><li><p><a class="ulink" href="http://www.sun.com/software/products/directory_srvr_ee/index.xml" target="_top"> 1196 Sun One Directory Server</a></p></li><li><p><a class="ulink" href="http://www.novell.com/products/edirectory/" target="_top">Novell eDirectory</a></p></li><li><p><a class="ulink" href="http://www-306.ibm.com/software/tivoli/products/directory-server/" target="_top">IBM 1197 Tivoli Directory Server</a></p></li><li><p><a class="ulink" href="http://www.redhat.com/software/rha/directory/" target="_top">Red Hat Directory 1198 Server</a></p></li><li><p><a class="ulink" href="http://www.linuxsecurity.com/content/view/119229" target="_top">Fedora Directory 1203 1199 Server</a></p></li></ul></div><p> 1204 1200 Two additional Samba resources that may prove to be helpful are: 1205 1201 </p><div class="itemizedlist"><ul type="disc"><li><p> 1206 <a class="indexterm" name="id3 56981"></a>1207 The <a href="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" target="_top">Samba-PDC-LDAP-HOWTO</a>1202 <a class="indexterm" name="id380005"></a> 1203 The <a class="ulink" href="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" target="_top">Samba-PDC-LDAP-HOWTO</a> 1208 1204 maintained by Ignacio Coupeau. 1209 1205 </p></li><li><p> 1210 <a class="indexterm" name="id3 56999"></a>1211 <a class="indexterm" name="id3 57006"></a>1212 <a class="indexterm" name="id3 57013"></a>1213 The NT migration scripts from <a href="http://samba.idealx.org/" target="_top">IDEALX</a> that are1206 <a class="indexterm" name="id380023"></a> 1207 <a class="indexterm" name="id380030"></a> 1208 <a class="indexterm" name="id380036"></a> 1209 The NT migration scripts from <a class="ulink" href="http://samba.idealx.org/" target="_top">IDEALX</a> that are 1214 1210 geared to manage users and groups in such a Samba-LDAP domain controller configuration. 1215 1211 Idealx also produced the smbldap-tools and the Interactive Console Management tool. 1216 </p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 57030"></a>Supported LDAP Servers</h4></div></div></div><p>1217 <a class="indexterm" name="id3 57037"></a>1218 <a class="indexterm" name="id3 57044"></a>1219 <a class="indexterm" name="id3 57051"></a>1220 <a class="indexterm" name="id3 57058"></a>1212 </p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id380053"></a>Supported LDAP Servers</h4></div></div></div><p> 1213 <a class="indexterm" name="id380061"></a> 1214 <a class="indexterm" name="id380068"></a> 1215 <a class="indexterm" name="id380075"></a> 1216 <a class="indexterm" name="id380081"></a> 1221 1217 The LDAP ldapsam code was developed and tested using the OpenLDAP 2.x server and 1222 1218 client libraries. The same code should work with Netscape's Directory Server and client SDK. 1223 1219 However, there are bound to be compile errors and bugs. These should not be hard to fix. 1224 Please submit fixes via the process outlined in <a href="bugreport.html" title="Chapter 40. Reporting Bugs">Reporting Bugs</a>.1220 Please submit fixes via the process outlined in <a class="link" href="bugreport.html" title="Chapter 40. Reporting Bugs">Reporting Bugs</a>. 1225 1221 </p><p> 1226 1222 Samba is capable of working with any standards-compliant LDAP server. 1227 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 57080"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div></div><p>1223 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id380104"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div></div><p> 1228 1224 Samba-3.0 includes the necessary schema file for OpenLDAP 2.x in the 1229 1225 <code class="filename">examples/LDAP/samba.schema</code> directory of the source code distribution … … 1241 1237 </pre><p> 1242 1238 </p><p> 1243 <a class="indexterm" name="id3 57110"></a>1244 <a class="indexterm" name="id3 57116"></a>1245 <a class="indexterm" name="id3 57123"></a>1239 <a class="indexterm" name="id380138"></a> 1240 <a class="indexterm" name="id380145"></a> 1241 <a class="indexterm" name="id380152"></a> 1246 1242 The <code class="filename">samba.schema</code> file has been formatted for OpenLDAP 2.0/2.1. 1247 1243 The Samba Team owns the OID space used by the above schema and recommends its use. 1248 1244 If you translate the schema to be used with Netscape DS, please submit the modified 1249 schema file as a patch to <a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>.1245 schema file as a patch to <a class="ulink" href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>. 1250 1246 </p><p> 1251 <a class="indexterm" name="id3 57147"></a>1252 <a class="indexterm" name="id3 57154"></a>1253 <a class="indexterm" name="id3 57161"></a>1254 <a class="indexterm" name="id3 57168"></a>1255 <a class="indexterm" name="id3 57174"></a>1256 <a class="indexterm" name="id3 57181"></a>1257 <a class="indexterm" name="id3 57188"></a>1247 <a class="indexterm" name="id380176"></a> 1248 <a class="indexterm" name="id380182"></a> 1249 <a class="indexterm" name="id380189"></a> 1250 <a class="indexterm" name="id380196"></a> 1251 <a class="indexterm" name="id380203"></a> 1252 <a class="indexterm" name="id380210"></a> 1253 <a class="indexterm" name="id380216"></a> 1258 1254 Just as the smbpasswd file is meant to store information that provides information 1259 1255 additional to a user's <code class="filename">/etc/passwd</code> entry, so is the sambaSamAccount … … 1264 1260 with the posixAccount ObjectClass outlined in RFC 2307. This is by design. 1265 1261 </p><p> 1266 <a class="indexterm" name="id3 57212"></a>1267 <a class="indexterm" name="id3 57219"></a>1268 <a class="indexterm" name="id3 57226"></a>1269 <a class="indexterm" name="id3 57233"></a>1270 <a class="indexterm" name="id3 57239"></a>1271 <a class="indexterm" name="id3 57246"></a>1272 <a class="indexterm" name="id3 57253"></a>1273 <a class="indexterm" name="id3 57260"></a>1274 <a class="indexterm" name="id3 57266"></a>1262 <a class="indexterm" name="id380240"></a> 1263 <a class="indexterm" name="id380247"></a> 1264 <a class="indexterm" name="id380254"></a> 1265 <a class="indexterm" name="id380261"></a> 1266 <a class="indexterm" name="id380268"></a> 1267 <a class="indexterm" name="id380274"></a> 1268 <a class="indexterm" name="id380281"></a> 1269 <a class="indexterm" name="id380288"></a> 1270 <a class="indexterm" name="id380295"></a> 1275 1271 In order to store all user account information (UNIX and Samba) in the directory, 1276 1272 it is necessary to use the sambaSamAccount and posixAccount ObjectClasses in … … 1281 1277 store all Samba account information in LDAP, but still maintain UNIX account 1282 1278 information in NIS while the network is transitioning to a full LDAP infrastructure. 1283 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 57286"></a>OpenLDAP Configuration</h4></div></div></div><p>1284 <a class="indexterm" name="id3 57294"></a>1285 <a class="indexterm" name="id3 57301"></a>1286 <a class="indexterm" name="id3 57308"></a>1287 <a class="indexterm" name="id3 57314"></a>1279 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id380315"></a>OpenLDAP Configuration</h4></div></div></div><p> 1280 <a class="indexterm" name="id380322"></a> 1281 <a class="indexterm" name="id380329"></a> 1282 <a class="indexterm" name="id380336"></a> 1283 <a class="indexterm" name="id380343"></a> 1288 1284 To include support for the sambaSamAccount object in an OpenLDAP directory 1289 1285 server, first copy the samba.schema file to slapd's configuration directory. … … 1294 1290 </pre><p> 1295 1291 </p><p> 1296 <a class="indexterm" name="id3 57348"></a>1297 <a class="indexterm" name="id3 57355"></a>1298 <a class="indexterm" name="id3 57362"></a>1299 <a class="indexterm" name="id3 57369"></a>1300 <a class="indexterm" name="id3 57376"></a>1301 <a class="indexterm" name="id3 57382"></a>1302 <a class="indexterm" name="id3 57389"></a>1303 <a class="indexterm" name="id3 57396"></a>1292 <a class="indexterm" name="id380377"></a> 1293 <a class="indexterm" name="id380384"></a> 1294 <a class="indexterm" name="id380390"></a> 1295 <a class="indexterm" name="id380397"></a> 1296 <a class="indexterm" name="id380404"></a> 1297 <a class="indexterm" name="id380410"></a> 1298 <a class="indexterm" name="id380417"></a> 1299 <a class="indexterm" name="id380424"></a> 1304 1300 Next, include the <code class="filename">samba.schema</code> file in <code class="filename">slapd.conf</code>. 1305 1301 The sambaSamAccount object contains two attributes that depend on other schema … … 1321 1317 </pre><p> 1322 1318 </p><p> 1323 <a class="indexterm" name="id3 57458"></a>1324 <a class="indexterm" name="id3 57465"></a>1325 <a class="indexterm" name="id3 57471"></a>1326 <a class="indexterm" name="id3 57478"></a>1319 <a class="indexterm" name="id380486"></a> 1320 <a class="indexterm" name="id380493"></a> 1321 <a class="indexterm" name="id380500"></a> 1322 <a class="indexterm" name="id380506"></a> 1327 1323 It is recommended that you maintain some indices on some of the most useful attributes, 1328 1324 as in the following example, to speed up searches made on sambaSamAccount ObjectClasses … … 1362 1358 <code class="prompt">root# </code><strong class="userinput"><code>/etc/init.d/slapd restart</code></strong> 1363 1359 </pre><p> 1364 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 57539"></a>Initialize the LDAP Database</h4></div></div></div><p>1365 <a class="indexterm" name="id3 57547"></a>1366 <a class="indexterm" name="id3 57553"></a>1367 <a class="indexterm" name="id3 57560"></a>1368 <a class="indexterm" name="id3 57567"></a>1360 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id380567"></a>Initialize the LDAP Database</h4></div></div></div><p> 1361 <a class="indexterm" name="id380575"></a> 1362 <a class="indexterm" name="id380582"></a> 1363 <a class="indexterm" name="id380588"></a> 1364 <a class="indexterm" name="id380595"></a> 1369 1365 Before you can add accounts to the LDAP database, you must create the account containers 1370 1366 that they will be stored in. The following LDIF file should be modified to match your … … 1428 1424 </pre><p> 1429 1425 </p><p> 1430 <a class="indexterm" name="id3 57608"></a>1431 <a class="indexterm" name="id3 57614"></a>1426 <a class="indexterm" name="id380624"></a> 1427 <a class="indexterm" name="id380631"></a> 1432 1428 The userPassword shown above should be generated using <code class="literal">slappasswd</code>. 1433 1429 </p><p> 1434 <a class="indexterm" name="id3 57631"></a>1435 <a class="indexterm" name="id3 57638"></a>1430 <a class="indexterm" name="id380648"></a> 1431 <a class="indexterm" name="id380654"></a> 1436 1432 The following command will then load the contents of the LDIF file into the LDAP 1437 1433 database. 1438 <a class="indexterm" name="id3 57646"></a>1434 <a class="indexterm" name="id380662"></a> 1439 1435 </p><pre class="screen"> 1440 1436 <code class="prompt">$ </code><strong class="userinput"><code>slapadd -v -l initldap.dif</code></strong> … … 1444 1440 as well as an admin password. 1445 1441 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> 1446 <a class="indexterm" name="id3 57677"></a>1442 <a class="indexterm" name="id380693"></a> 1447 1443 Before Samba can access the LDAP server, you need to store the LDAP admin password 1448 1444 in the Samba-3 <code class="filename">secrets.tdb</code> database by: 1449 <a class="indexterm" name="id3 57690"></a>1445 <a class="indexterm" name="id380707"></a> 1450 1446 </p><pre class="screen"> 1451 1447 <code class="prompt">root# </code><strong class="userinput"><code>smbpasswd -w <em class="replaceable"><code>secret</code></em></code></strong> 1452 1448 </pre><p> 1453 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 57718"></a>Configuring Samba</h4></div></div></div><p>1454 <a class="indexterm" name="id3 57725"></a>1455 <a class="indexterm" name="id3 57732"></a>1449 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id380734"></a>Configuring Samba</h4></div></div></div><p> 1450 <a class="indexterm" name="id380742"></a> 1451 <a class="indexterm" name="id380749"></a> 1456 1452 The following parameters are available in <code class="filename">smb.conf</code> only if your version of Samba was built with 1457 LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found. The 1453 LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found. The 1458 1454 best method to verify that Samba was built with LDAP support is: 1459 1455 </p><pre class="screen"> … … 1472 1468 and libraries were not found during compilation. 1473 1469 </p><p>LDAP-related smb.conf options include these: 1474 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id3 57783"></a><em class="parameter"><code>passdb backend = ldapsam:url</code></em></td></tr><tr><td><a class="indexterm" name="id357796"></a><em class="parameter"><code>ldap admin dn</code></em></td></tr><tr><td><a class="indexterm" name="id357808"></a><em class="parameter"><code>ldap delete dn</code></em></td></tr><tr><td><a class="indexterm" name="id357821"></a><em class="parameter"><code>ldap filter</code></em></td></tr><tr><td><a class="indexterm" name="id357833"></a><em class="parameter"><code>ldap group suffix</code></em></td></tr><tr><td><a class="indexterm" name="id357846"></a><em class="parameter"><code>ldap idmap suffix</code></em></td></tr><tr><td><a class="indexterm" name="id357858"></a><em class="parameter"><code>ldap machine suffix</code></em></td></tr><tr><td><a class="indexterm" name="id357871"></a><em class="parameter"><code>ldap passwd sync</code></em></td></tr><tr><td><a class="indexterm" name="id357883"></a><em class="parameter"><code>ldap ssl</code></em></td></tr><tr><td><a class="indexterm" name="id357896"></a><em class="parameter"><code>ldap suffix</code></em></td></tr><tr><td><a class="indexterm" name="id357908"></a><em class="parameter"><code>ldap user suffix</code></em></td></tr><tr><td><a class="indexterm" name="id357921"></a><em class="parameter"><code>ldap replication sleep</code></em></td></tr><tr><td><a class="indexterm" name="id357933"></a><em class="parameter"><code>ldap timeout</code></em></td></tr><tr><td><a class="indexterm" name="id357946"></a><em class="parameter"><code>ldap page size</code></em></td></tr></table><p>1470 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id380799"></a><em class="parameter"><code>passdb backend = ldapsam:url</code></em></td></tr><tr><td><a class="indexterm" name="id380811"></a></td></tr><tr><td><a class="indexterm" name="id380818"></a></td></tr><tr><td><a class="indexterm" name="id380825"></a></td></tr><tr><td><a class="indexterm" name="id380831"></a></td></tr><tr><td><a class="indexterm" name="id380838"></a></td></tr><tr><td><a class="indexterm" name="id380845"></a></td></tr><tr><td><a class="indexterm" name="id380852"></a></td></tr><tr><td><a class="indexterm" name="id380859"></a></td></tr><tr><td><a class="indexterm" name="id380865"></a></td></tr><tr><td><a class="indexterm" name="id380872"></a></td></tr><tr><td><a class="indexterm" name="id380879"></a></td></tr><tr><td><a class="indexterm" name="id380886"></a></td></tr><tr><td><a class="indexterm" name="id380893"></a></td></tr></table><p> 1475 1471 </p><p> 1476 These are described in the <code class="filename">smb.conf</code> man page and so are not repeated here. However, an example 1477 for use with an LDAP directory is shown in <a href="passdb.html#confldapex" title="Example 11.2. Configuration with LDAP">the Configuration with LDAP.</a>1478 </p><div class="example"><a name="confldapex"></a><p class="title"><b>Example 11.2. Configuration with LDAP</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id3 58001"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id358014"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id358026"></a><em class="parameter"><code>netbios name = MORIA</code></em></td></tr><tr><td><a class="indexterm" name="id358039"></a><em class="parameter"><code>workgroup = NOLDOR</code></em></td></tr><tr><td># LDAP related parameters:</td></tr><tr><td># Define the DN used when binding to the LDAP servers.</td></tr><tr><td># The password for this DN is not stored in smb.conf</td></tr><tr><td># Set it using 'smbpasswd -w secret' to store the</td></tr><tr><td># passphrase in the secrets.tdb file.</td></tr><tr><td># If the "ldap admin dn" value changes, it must be reset.</td></tr><tr><td><a class="indexterm" name="id358074"></a><em class="parameter"><code>ldap admin dn = "cn=Manager,dc=quenya,dc=org"</code></em></td></tr><tr><td># SSL directory connections can be configured by:</td></tr><tr><td># ('off', 'start tls', or 'on' (default))</td></tr><tr><td><a class="indexterm" name="id358094"></a><em class="parameter"><code>ldap ssl = start tls</code></em></td></tr><tr><td># syntax: passdb backend = ldapsam:ldap://server-name[:port]</td></tr><tr><td><a class="indexterm" name="id358110"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://frodo.quenya.org</code></em></td></tr><tr><td># smbpasswd -x delete the entire dn-entry</td></tr><tr><td><a class="indexterm" name="id358127"></a><em class="parameter"><code>ldap delete dn = no</code></em></td></tr><tr><td># The machine and user suffix are added to the base suffix</td></tr><tr><td># wrote WITHOUT quotes. NULL suffixes by default</td></tr><tr><td><a class="indexterm" name="id358147"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id358160"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id358172"></a><em class="parameter"><code>ldap machine suffix = ou=Computers</code></em></td></tr><tr><td># Trust UNIX account information in LDAP</td></tr><tr><td># (see the smb.conf man page for details)</td></tr><tr><td># Specify the base DN to use when searching the directory</td></tr><tr><td><a class="indexterm" name="id358196"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id358211"></a>Accounts and Groups Management</h4></div></div></div><p>1479 <a class="indexterm" name="id3 58219"></a>1480 <a class="indexterm" name="id3 58226"></a>1472 These are described in the <code class="filename">smb.conf</code> man page and so are not repeated here. However, an example 1473 for use with an LDAP directory is shown in <a class="link" href="passdb.html#confldapex" title="Example 11.2. Configuration with LDAP">the Configuration with LDAP.</a> 1474 </p><div class="example"><a name="confldapex"></a><p class="title"><b>Example 11.2. Configuration with LDAP</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id380942"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id380954"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id380965"></a><em class="parameter"><code>netbios name = MORIA</code></em></td></tr><tr><td><a class="indexterm" name="id380977"></a><em class="parameter"><code>workgroup = NOLDOR</code></em></td></tr><tr><td># LDAP related parameters:</td></tr><tr><td># Define the DN used when binding to the LDAP servers.</td></tr><tr><td># The password for this DN is not stored in smb.conf</td></tr><tr><td># Set it using 'smbpasswd -w secret' to store the</td></tr><tr><td># passphrase in the secrets.tdb file.</td></tr><tr><td># If the "ldap admin dn" value changes, it must be reset.</td></tr><tr><td><a class="indexterm" name="id381010"></a><em class="parameter"><code>ldap admin dn = "cn=Manager,dc=quenya,dc=org"</code></em></td></tr><tr><td># SSL directory connections can be configured by:</td></tr><tr><td># ('off', 'start tls', or 'on' (default))</td></tr><tr><td><a class="indexterm" name="id381030"></a><em class="parameter"><code>ldap ssl = start tls</code></em></td></tr><tr><td># syntax: passdb backend = ldapsam:ldap://server-name[:port]</td></tr><tr><td><a class="indexterm" name="id381045"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://frodo.quenya.org</code></em></td></tr><tr><td># smbpasswd -x delete the entire dn-entry</td></tr><tr><td><a class="indexterm" name="id381060"></a><em class="parameter"><code>ldap delete dn = no</code></em></td></tr><tr><td># The machine and user suffix are added to the base suffix</td></tr><tr><td># wrote WITHOUT quotes. NULL suffixes by default</td></tr><tr><td><a class="indexterm" name="id381080"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id381091"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id381103"></a><em class="parameter"><code>ldap machine suffix = ou=Computers</code></em></td></tr><tr><td># Trust UNIX account information in LDAP</td></tr><tr><td># (see the smb.conf man page for details)</td></tr><tr><td># Specify the base DN to use when searching the directory</td></tr><tr><td><a class="indexterm" name="id381126"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id381139"></a>Accounts and Groups Management</h4></div></div></div><p> 1475 <a class="indexterm" name="id381147"></a> 1476 <a class="indexterm" name="id381154"></a> 1481 1477 Because user accounts are managed through the sambaSamAccount ObjectClass, you should 1482 1478 modify your existing administration tools to deal with sambaSamAccount attributes. 1483 1479 </p><p> 1484 <a class="indexterm" name="id3 58240"></a>1485 <a class="indexterm" name="id3 58247"></a>1486 <a class="indexterm" name="id3 58254"></a>1480 <a class="indexterm" name="id381168"></a> 1481 <a class="indexterm" name="id381175"></a> 1482 <a class="indexterm" name="id381182"></a> 1487 1483 Machine accounts are managed with the sambaSamAccount ObjectClass, just 1488 1484 like user accounts. However, it is up to you to store those accounts … … 1493 1489 configuration file). 1494 1490 </p><p> 1495 <a class="indexterm" name="id3 58280"></a>1496 <a class="indexterm" name="id3 58287"></a>1497 <a class="indexterm" name="id3 58294"></a>1498 <a class="indexterm" name="id3 58300"></a>1491 <a class="indexterm" name="id381208"></a> 1492 <a class="indexterm" name="id381215"></a> 1493 <a class="indexterm" name="id381222"></a> 1494 <a class="indexterm" name="id381228"></a> 1499 1495 In Samba-3, the group management system is based on POSIX 1500 1496 groups. This means that Samba makes use of the posixGroup ObjectClass. … … 1502 1498 groups). Samba-3 knows only about <code class="constant">Domain Groups</code> 1503 1499 and, unlike MS Windows 2000 and Active Directory, Samba-3 does not 1504 support nested groups. 1505 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 58316"></a>Security and sambaSamAccount</h4></div></div></div><p>1506 <a class="indexterm" name="id3 58323"></a>1500 support nested groups. 1501 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id381244"></a>Security and sambaSamAccount</h4></div></div></div><p> 1502 <a class="indexterm" name="id381252"></a> 1507 1503 There are two important points to remember when discussing the security 1508 1504 of sambaSAMAccount entries in the directory. 1509 1505 </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Never</em></span> retrieve the SambaLMPassword or 1510 <a class="indexterm" name="id3 58341"></a>1506 <a class="indexterm" name="id381269"></a> 1511 1507 SambaNTPassword attribute values over an unencrypted LDAP session.</p></li><li><p><span class="emphasis"><em>Never</em></span> allow non-admin users to 1512 1508 view the SambaLMPassword or SambaNTPassword attribute values.</p></li></ul></div><p> 1513 <a class="indexterm" name="id3 58360"></a>1514 <a class="indexterm" name="id3 58367"></a>1515 <a class="indexterm" name="id3 58374"></a>1509 <a class="indexterm" name="id381288"></a> 1510 <a class="indexterm" name="id381295"></a> 1511 <a class="indexterm" name="id381302"></a> 1516 1512 These password hashes are clear-text equivalents and can be used to impersonate 1517 1513 the user without deriving the original clear-text strings. For more information 1518 on the details of LM/NT password hashes, refer to <a href="passdb.html" title="Chapter 11. Account Information Databases">the1514 on the details of LM/NT password hashes, refer to <a class="link" href="passdb.html" title="Chapter 11. Account Information Databases">the 1519 1515 Account Information Database section</a>. 1520 1516 </p><p> 1521 <a class="indexterm" name="id3 58393"></a>1522 <a class="indexterm" name="id3 58400"></a>1523 <a class="indexterm" name="id3 58406"></a>1524 <a class="indexterm" name="id3 58413"></a>1525 To remedy the first security issue, the <a class=" indexterm" name="id358420"></a>ldap ssl<code class="filename">smb.conf</code>1526 parameter defaults to require an encrypted session (<a class=" indexterm" name="id358434"></a>ldap ssl = on) using the default port of <code class="constant">636</code> when1517 <a class="indexterm" name="id381321"></a> 1518 <a class="indexterm" name="id381328"></a> 1519 <a class="indexterm" name="id381334"></a> 1520 <a class="indexterm" name="id381341"></a> 1521 To remedy the first security issue, the <a class="link" href="smb.conf.5.html#LDAPSSL">ldap ssl</a> <code class="filename">smb.conf</code> 1522 parameter defaults to require an encrypted session (<a class="link" href="smb.conf.5.html#LDAPSSL">ldap ssl = on</a>) using the default port of <code class="constant">636</code> when 1527 1523 contacting the directory server. When using an OpenLDAP server, it 1528 1524 is possible to use the StartTLS LDAP extended operation in the place of LDAPS. 1529 1525 In either case, you are strongly encouraged to use secure communications protocols 1530 (so do not set <a class=" indexterm" name="id358447"></a>ldap ssl = off).1526 (so do not set <a class="link" href="smb.conf.5.html#LDAPSSL">ldap ssl = off</a>). 1531 1527 </p><p> 1532 <a class="indexterm" name="id3 58457"></a>1533 <a class="indexterm" name="id3 58464"></a>1534 <a class="indexterm" name="id3 58471"></a>1528 <a class="indexterm" name="id381395"></a> 1529 <a class="indexterm" name="id381402"></a> 1530 <a class="indexterm" name="id381409"></a> 1535 1531 Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS 1536 1532 extended operation. However, the OpenLDAP library still provides support for 1537 1533 the older method of securing communication between clients and servers. 1538 1534 </p><p> 1539 <a class="indexterm" name="id3 58483"></a>1540 <a class="indexterm" name="id3 58490"></a>1541 <a class="indexterm" name="id3 58496"></a>1535 <a class="indexterm" name="id381421"></a> 1536 <a class="indexterm" name="id381428"></a> 1537 <a class="indexterm" name="id381434"></a> 1542 1538 The second security precaution is to prevent non-administrative users from 1543 1539 harvesting password hashes from the directory. This can be done using the … … 1550 1546 by * none 1551 1547 </pre><p> 1552 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 58523"></a>LDAP Special Attributes for sambaSamAccounts</h4></div></div></div><p> The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: <a href="passdb.html#attribobjclPartA" title="Table 11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A">Part A</a>, and <a href="passdb.html#attribobjclPartB" title="Table 11.4. Attributes in the sambaSamAccount ObjectClass (LDAP), Part B">Part B</a>.1548 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id381461"></a>LDAP Special Attributes for sambaSamAccounts</h4></div></div></div><p> The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: <a class="link" href="passdb.html#attribobjclPartA" title="Table 11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A">Part A</a>, and <a class="link" href="passdb.html#attribobjclPartB" title="Table 11.4. Attributes in the sambaSamAccount ObjectClass (LDAP), Part B">Part B</a>. 1553 1549 </p><div class="table"><a name="attribobjclPartA"></a><p class="title"><b>Table 11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A</b></p><div class="table-contents"><table summary="Attributes in the sambaSamAccount ObjectClass (LDAP), Part A" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left"><code class="constant">sambaLMPassword</code></td><td align="justify">The LanMan password 16-byte hash stored as a character 1554 1550 representation of a hexadecimal string.</td></tr><tr><td align="left"><code class="constant">sambaNTPassword</code></td><td align="justify">The NT password 16-byte hash stored as a character … … 1560 1556 and D (disabled).</td></tr><tr><td align="left"><code class="constant">sambaLogonTime</code></td><td align="justify">Integer value currently unused.</td></tr><tr><td align="left"><code class="constant">sambaLogoffTime</code></td><td align="justify">Integer value currently unused.</td></tr><tr><td align="left"><code class="constant">sambaKickoffTime</code></td><td align="justify">Specifies the time (UNIX time format) when the user 1561 1557 will be locked down and cannot login any longer. If this attribute is omitted, then the account will never expire. 1562 Using this attribute together with shadowExpire of the shadowAccount ObjectClass will enable accounts to 1558 Using this attribute together with shadowExpire of the shadowAccount ObjectClass will enable accounts to 1563 1559 expire completely on an exact date.</td></tr><tr><td align="left"><code class="constant">sambaPwdCanChange</code></td><td align="justify">Specifies the time (UNIX time format) 1564 1560 after which the user is allowed to change his password. If this attribute is not set, the user will be free … … 1570 1566 smb.conf(5) man page for more information.</td></tr><tr><td align="left"><code class="constant">sambaLogonScript</code></td><td align="justify">The sambaLogonScript property specifies the path of 1571 1567 the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path 1572 is relative to the netlogon share. Refer to the <a class=" indexterm" name="id358694"></a>logon scriptparameter in the1568 is relative to the netlogon share. Refer to the <a class="link" href="smb.conf.5.html#LOGONSCRIPT">logon script</a> parameter in the 1573 1569 <code class="filename">smb.conf</code> man page for more information.</td></tr><tr><td align="left"><code class="constant">sambaProfilePath</code></td><td align="justify">Specifies a path to the user's profile. 1574 1570 This value can be a null string, a local absolute path, or a UNC path. Refer to the 1575 <a class=" indexterm" name="id358717"></a>logon pathparameter in the <code class="filename">smb.conf</code> man page for more information.</td></tr><tr><td align="left"><code class="constant">sambaHomePath</code></td><td align="justify">The sambaHomePath property specifies the path of1571 <a class="link" href="smb.conf.5.html#LOGONPATH">logon path</a> parameter in the <code class="filename">smb.conf</code> man page for more information.</td></tr><tr><td align="left"><code class="constant">sambaHomePath</code></td><td align="justify">The sambaHomePath property specifies the path of 1576 1572 the home directory for the user. The string can be null. If sambaHomeDrive is set and specifies 1577 1573 a drive letter, sambaHomePath should be a UNC path. The path must be a network … … 1585 1581 The Windows equivalent of UNIX UIDs.</td></tr><tr><td align="left"><code class="constant">sambaPrimaryGroupSID</code></td><td align="justify">The security identifier (SID) of the primary group 1586 1582 of the user.</td></tr><tr><td align="left"><code class="constant">sambaDomainName</code></td><td align="justify">Domain the user is part of.</td></tr></tbody></table></div></div><br class="table-break"><p> 1587 <a class="indexterm" name="id3 58833"></a>1588 <a class="indexterm" name="id3 58839"></a>1583 <a class="indexterm" name="id381779"></a> 1584 <a class="indexterm" name="id381785"></a> 1589 1585 The majority of these parameters are only used when Samba is acting as a PDC of 1590 a domain (refer to <a href="samba-pdc.html" title="Chapter 4. Domain Control">Domain Control</a>, for details on1586 a domain (refer to <a class="link" href="samba-pdc.html" title="Chapter 4. Domain Control">Domain Control</a>, for details on 1591 1587 how to configure Samba as a PDC). The following four attributes 1592 1588 are only stored with the sambaSamAccount entry if the values are non-default values: 1593 </p><div class="itemizedlist"><a class="indexterm" name="id3 58858"></a><a class="indexterm" name="id358865"></a><a class="indexterm" name="id358872"></a><a class="indexterm" name="id358879"></a><ul type="disc"><li><p>sambaHomePath</p></li><li><p>sambaLogonScript</p></li><li><p>sambaProfilePath</p></li><li><p>sambaHomeDrive</p></li></ul></div><p>1594 <a class="indexterm" name="id3 58907"></a>1595 <a class="indexterm" name="id3 58914"></a>1596 <a class="indexterm" name="id3 58920"></a>1589 </p><div class="itemizedlist"><a class="indexterm" name="id381805"></a><a class="indexterm" name="id381812"></a><a class="indexterm" name="id381818"></a><a class="indexterm" name="id381825"></a><ul type="disc"><li><p>sambaHomePath</p></li><li><p>sambaLogonScript</p></li><li><p>sambaProfilePath</p></li><li><p>sambaHomeDrive</p></li></ul></div><p> 1590 <a class="indexterm" name="id381853"></a> 1591 <a class="indexterm" name="id381860"></a> 1592 <a class="indexterm" name="id381867"></a> 1597 1593 These attributes are only stored with the sambaSamAccount entry if 1598 1594 the values are non-default values. For example, assume MORIA has now been 1599 configured as a PDC and that <a class=" indexterm" name="id358929"></a>logon home = \\%L\%uwas defined in1595 configured as a PDC and that <a class="link" href="smb.conf.5.html#LOGONHOME">logon home = \\%L\%u</a> was defined in 1600 1596 its <code class="filename">smb.conf</code> file. When a user named “<span class="quote">becky</span>” logs on to the domain, 1601 the <a class=" indexterm" name="id358946"></a>logon homestring is expanded to \\MORIA\becky.1597 the <a class="link" href="smb.conf.5.html#LOGONHOME">logon home</a> string is expanded to \\MORIA\becky. 1602 1598 If the smbHome attribute exists in the entry “<span class="quote">uid=becky,ou=People,dc=samba,dc=org</span>”, 1603 1599 this value is used. However, if this attribute does not exist, then the value 1604 of the <a class=" indexterm" name="id358958"></a>logon homeparameter is used in its place. Samba1600 of the <a class="link" href="smb.conf.5.html#LOGONHOME">logon home</a> parameter is used in its place. Samba 1605 1601 will only write the attribute value to the directory entry if the value is 1606 1602 something other than the default (e.g., <code class="filename">\\MOBY\becky</code>). 1607 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 58975"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div></div><p>1603 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id381932"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div></div><p> 1608 1604 The following is a working LDIF that demonstrates the use of the SambaSamAccount ObjectClass: 1609 1605 </p><pre class="programlisting"> … … 1650 1646 sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7 1651 1647 </pre><p> 1652 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 59011"></a>Password Synchronization</h4></div></div></div><p>1648 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id381969"></a>Password Synchronization</h4></div></div></div><p> 1653 1649 Samba-3 and later can update the non-Samba (LDAP) password stored with an account. When 1654 1650 using pam_ldap, this allows changing both UNIX and Windows passwords at once. 1655 </p><p>The <a class=" indexterm" name="id359024"></a>ldap passwd syncoptions can have the values shown in1656 <a href="passdb.html#ldappwsync" title="Table 11.5. Possible ldap passwd sync Values">Possible <span class="emphasis"><em>ldap passwd sync</em></span> Values</a>.</p><div class="table"><a name="ldappwsync"></a><p class="title"><b>Table 11.5. Possible <em class="parameter"><code>ldap passwd sync</code></em> Values</b></p><div class="table-contents"><table summary="Possible ldap passwd sync Values" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Value</th><th align="center">Description</th></tr></thead><tbody><tr><td align="left">yes</td><td align="justify"><p>When the user changes his password, update1651 </p><p>The <a class="link" href="smb.conf.5.html#LDAPPASSWDSYNC">ldap passwd sync</a> options can have the values shown in 1652 <a class="link" href="passdb.html#ldappwsync" title="Table 11.5. Possible ldap passwd sync Values">Possible <span class="emphasis"><em>ldap passwd sync</em></span> Values</a>.</p><div class="table"><a name="ldappwsync"></a><p class="title"><b>Table 11.5. Possible <em class="parameter"><code>ldap passwd sync</code></em> Values</b></p><div class="table-contents"><table summary="Possible ldap passwd sync Values" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Value</th><th align="center">Description</th></tr></thead><tbody><tr><td align="left">yes</td><td align="justify"><p>When the user changes his password, update 1657 1653 <code class="constant">SambaNTPassword</code>, <code class="constant">SambaLMPassword</code>, 1658 1654 and the <code class="constant">password</code> fields.</p></td></tr><tr><td align="left">no</td><td align="justify"><p>Only update <code class="constant">SambaNTPassword</code> and 1659 1655 <code class="constant">SambaLMPassword</code>.</p></td></tr><tr><td align="left">only</td><td align="justify"><p>Only update the LDAP password and let the LDAP server 1660 1656 worry about the other fields. This option is only available on some LDAP servers and 1661 only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.</p></td></tr></tbody></table></div></div><br class="table-break"><p>More information can be found in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id3 59153"></a>Using OpenLDAP Overlay for Password Syncronization</h4></div></div></div><p>1657 only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.</p></td></tr></tbody></table></div></div><br class="table-break"><p>More information can be found in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id382114"></a>Using OpenLDAP Overlay for Password Syncronization</h4></div></div></div><p> 1662 1658 Howard Chu has written a special overlay called <code class="literal">smbk5pwd</code>. This tool modifies the 1663 1659 <code class="literal">SambaNTPassword</code>, <code class="literal">SambaLMPassword</code> and <code class="literal">Heimdal</code> … … 1667 1663 <code class="filename">contrib/slapd-modules/smbk5pwd</code> subdirectory. This module can also be used with 1668 1664 OpenLDAP-2.2. 1669 </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id3 59200"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id359206"></a>Users Cannot Logon</h3></div></div></div><p>“<span class="quote">I've installed Samba, but now I can't log on with my UNIX account! </span>”</p><p>Make sure your user has been added to the current Samba <a class="indexterm" name="id359219"></a>passdb backend.1670 Read the <a href="passdb.html#acctmgmttools" title="Account Management Tools">Account Management Tools,</a> for details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id359237"></a>Configuration of <em class="parameter"><code>auth methods</code></em></h3></div></div></div><p>1671 When explicitly setting an <a class=" indexterm" name="id359250"></a>auth methodsparameter,1665 </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id382162"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id382168"></a>Users Cannot Logon</h3></div></div></div><p>“<span class="quote">I've installed Samba, but now I can't log on with my UNIX account! </span>”</p><p>Make sure your user has been added to the current Samba <a class="link" href="smb.conf.5.html#PASSDBBACKEND">passdb backend</a>. 1666 Read the <a class="link" href="passdb.html#acctmgmttools" title="Account Management Tools">Account Management Tools,</a> for details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id382202"></a>Configuration of <em class="parameter"><code>auth methods</code></em></h3></div></div></div><p> 1667 When explicitly setting an <a class="link" href="smb.conf.5.html#AUTHMETHODS">auth methods</a> parameter, 1672 1668 <em class="parameter"><code>guest</code></em> must be specified as the first entry on the line 1673 for example, <a class=" indexterm" name="id359266"></a>auth methods = guest sam.1669 for example, <a class="link" href="smb.conf.5.html#AUTHMETHODS">auth methods = guest sam</a>. 1674 1670 </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="groupmapping.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 10. Network Browsing </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 12. Group Mapping: MS Windows and UNIX</td></tr></table></div></body></html>
Note:
See TracChangeset
for help on using the changeset viewer.
