1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 10. Account Information Databases</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.68.1"><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 9. Network Browsing"><link rel="next" href="groupmapping.html" title="Chapter 11. 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 10. 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 10. 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#id2553673">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2553709">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2553893">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#id2554621">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2555148">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#id2555694">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2556106">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#id2556547">The <span><strong class="command">smbpasswd</strong></span> Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The <span><strong class="command">pdbedit</strong></span> Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2559092">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2559169">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2559245">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2559514">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2559672">ldapsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2562246">MySQL</a></span></dt><dt><span class="sect2"><a href="passdb.html#XMLpassdb">XML</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2563268">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2563274">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2563306">Users Being Added to the Wrong Backend Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2563395">Configuration of <em class="parameter"><code>auth methods</code></em></a></span></dt></dl></dd></dl></div><p>
2 <a class="indexterm" name="id2553474"></a>
3 <a class="indexterm" name="id2553481"></a>
4 <a class="indexterm" name="id2553488"></a>
5 <a class="indexterm" name="id2553494"></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.
11 <a class="indexterm" name="id2553510"></a>
12 <a class="indexterm" name="id2553517"></a>
13 <a class="indexterm" name="id2553524"></a>
14 <a class="indexterm" name="id2553531"></a>
15 <a class="indexterm" name="id2553537"></a>
16 <a class="indexterm" name="id2553544"></a>
17 The three passdb backends that are fully maintained (actively supported) by the Samba Team are:
18 <code class="literal">smbpasswd</code> (being obsoleted), <code class="literal">tdbsam</code> (a tdb-based binary file format),
19 and <code class="literal">ldapsam</code> (LDAP directory). Of these, only the <code class="literal">ldapsam</code> backend
20 stores both POSIX (UNIX) and Samba user and group account information in a single repository. The
21 <code class="literal">smbpasswd</code> and <code class="literal">tdbsam</code> backends store only Samba user accounts.
23 In a strict sense, there are three supported account storage and access systems. One of these is considered
24 obsolete (smbpasswd). It is recommended to use the <code class="literal">tdbsam</code> method for all simple systems. Use
25 <code class="literal">ldapsam</code> for larger and more complex networks.
27 <a class="indexterm" name="id2553615"></a>
28 <a class="indexterm" name="id2553622"></a>
29 <a class="indexterm" name="id2553629"></a>
30 <a class="indexterm" name="id2553636"></a>
31 <a class="indexterm" name="id2553643"></a>
32 <a class="indexterm" name="id2553650"></a>
33 <a class="indexterm" name="id2553657"></a>
34 In a strict and literal sense, the passdb backends are account storage mechanisms (or methods) alone. The choice
35 of terminology can be misleading, however we are stuck with this choice of wording. This chapter documents the
36 nature of the account storage system with a focus on user and trust accounts. Trust accounts have two forms,
37 machine trust accounts (computer accounts) and interdomain trust accounts. These are all treated as user-like
39 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2553673"></a>Features and Benefits</h2></div></div></div><p>
40 Samba-3 provides for complete backward compatibility with Samba-2.2.x functionality
42 <a class="indexterm" name="id2553682"></a>
43 <a class="indexterm" name="id2553692"></a>
44 <a class="indexterm" name="id2553701"></a>
45 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553709"></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="id2553726"></a>
47 <a class="indexterm" name="id2553733"></a>
48 <a class="indexterm" name="id2553740"></a>
49 <a class="indexterm" name="id2553747"></a>
50 <a class="indexterm" name="id2553754"></a>
51 This isn't really a backend at all, but is listed here for simplicity. Samba can be configured to pass
52 plaintext authentication requests to the traditional UNIX/Linux <code class="filename">/etc/passwd</code> and
53 <code class="filename">/etc/shadow</code>-style subsystems. On systems that have Pluggable Authentication Modules
54 (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 plaintext
57 </p></dd><dt><span class="term">smbpasswd</span></dt><dd><p>
58 <a class="indexterm" name="id2553801"></a>
59 <a class="indexterm" name="id2553808"></a>
60 <a class="indexterm" name="id2553815"></a>
61 <a class="indexterm" name="id2553822"></a>
62 This option allows continued use of the <code class="filename">smbpasswd</code>
63 file that maintains a plain ASCII (text) layout that includes the MS Windows
64 LanMan and NT-encrypted passwords as well as a field that stores some
65 account information. This form of password backend does not store any of
66 the MS Windows NT/200x SAM (Security Account Manager) information required to
67 provide the extended controls that are needed for more comprehensive
68 interoperation with MS Windows NT4/200x servers.
70 This backend should be used only for backward compatibility with older
71 versions of Samba. It may be deprecated in future releases.
72 </p></dd><dt><span class="term">ldapsam_compat (Samba-2.2 LDAP Compatibility)</span></dt><dd><p>
73 <a class="indexterm" name="id2553861"></a>
74 <a class="indexterm" name="id2553868"></a>
75 <a class="indexterm" name="id2553875"></a>
76 There is a password backend option that allows continued operation with
77 an existing OpenLDAP backend that uses the Samba-2.2.x LDAP schema extension.
78 This option is provided primarily as a migration tool, although there is
79 no reason to force migration at this time. This tool will eventually
81 </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2553893"></a>New Account Storage Systems</h3></div></div></div><p>
82 Samba-3 introduces a number of new password backend capabilities.
83 <a class="indexterm" name="id2553902"></a>
84 <a class="indexterm" name="id2553911"></a>
85 <a class="indexterm" name="id2553920"></a>
86 <a class="indexterm" name="id2553929"></a>
87 </p><div class="variablelist"><dl><dt><span class="term">tdbsam</span></dt><dd><p>
88 <a class="indexterm" name="id2553951"></a>
89 <a class="indexterm" name="id2553958"></a>
90 <a class="indexterm" name="id2553964"></a>
91 This backend provides a rich database backend for local servers. This
92 backend is not suitable for multiple domain controllers (i.e., PDC + one
93 or more BDC) installations.
95 <a class="indexterm" name="id2553977"></a>
96 <a class="indexterm" name="id2553984"></a>
97 <a class="indexterm" name="id2553991"></a>
98 <a class="indexterm" name="id2553998"></a>
99 <a class="indexterm" name="id2554004"></a>
100 <a class="indexterm" name="id2554012"></a>
101 The <span class="emphasis"><em>tdbsam</em></span> password backend stores the old <span class="emphasis"><em>
102 smbpasswd</em></span> information plus the extended MS Windows NT/200x
103 SAM information into a binary format TDB (trivial database) file.
104 The inclusion of the extended information makes it possible for Samba-3
105 to implement the same account and system access controls that are possible
106 with MS Windows NT4/200x-based systems.
108 <a class="indexterm" name="id2554035"></a>
109 <a class="indexterm" name="id2554042"></a>
110 <a class="indexterm" name="id2554049"></a>
111 The inclusion of the <span class="emphasis"><em>tdbsam</em></span> capability is a direct
112 response to user requests to allow simple site operation without the overhead
113 of the complexities of running OpenLDAP. It is recommended to use this only
114 for sites that have fewer than 250 users. For larger sites or implementations,
115 the use of OpenLDAP or of Active Directory integration is strongly recommended.
116 </p></dd><dt><span class="term">ldapsam</span></dt><dd><p>
117 <a class="indexterm" name="id2554077"></a>
118 <a class="indexterm" name="id2554084"></a>
119 This provides a rich directory backend for distributed account installation.
121 <a class="indexterm" name="id2554096"></a>
122 <a class="indexterm" name="id2554103"></a>
123 <a class="indexterm" name="id2554110"></a>
124 <a class="indexterm" name="id2554117"></a>
125 <a class="indexterm" name="id2554124"></a>
126 Samba-3 has a new and extended LDAP implementation that requires configuration
127 of OpenLDAP with a new format Samba schema. The new format schema file is
128 included in the <code class="filename">examples/LDAP</code> directory of the Samba distribution.
130 <a class="indexterm" name="id2554146"></a>
131 <a class="indexterm" name="id2554153"></a>
132 <a class="indexterm" name="id2554160"></a>
133 <a class="indexterm" name="id2554166"></a>
134 <a class="indexterm" name="id2554174"></a>
135 The new LDAP implementation significantly expands the control abilities that
136 were possible with prior versions of Samba. It is now possible to specify
137 “<span class="quote">per-user</span>” profile settings, home directories, account access controls, and
138 much more. Corporate sites will see that the Samba Team has listened to their
139 requests both for capability and greater scalability.
140 </p></dd><dt><span class="term">mysqlsam (MySQL-based backend)</span></dt><dd><p>
141 <a class="indexterm" name="id2554203"></a>
142 <a class="indexterm" name="id2554210"></a>
143 <a class="indexterm" name="id2554217"></a>
144 It is expected that the MySQL-based SAM will be very popular in some corners.
145 This database backend will be of considerable interest to sites that want to
146 leverage existing MySQL technology.
147 </p></dd><dt><span class="term">pgsqlsam (PostGreSQL-based backend)</span></dt><dd><p>
148 <a class="indexterm" name="id2554239"></a>
149 <a class="indexterm" name="id2554246"></a>
150 Makes use of a PostgreSQL database to store account information. This backend is largely undocumented at
151 the moment, though its configuration is very similar to that of the mysqlsam backend.
152 </p></dd><dt><span class="term">xmlsam (XML-based datafile)</span></dt><dd><p>
153 <a class="indexterm" name="id2554269"></a>
154 <a class="indexterm" name="id2554276"></a>
155 <a class="indexterm" name="id2554283"></a>
156 Allows the account and password data to be stored in an XML format
157 data file. This backend cannot be used for normal operation, it can only
158 be used in conjunction with <span><strong class="command">pdbedit</strong></span>'s pdb2pdb
159 functionality. The Document Type Definition (DTD) file that is used
160 might be subject to changes in the future. (See the XML <a href="http://www.brics.dk/~amoeller/XML/schemas/" target="_top">reference</a> for a definition
163 <a class="indexterm" name="id2554311"></a>
164 <a class="indexterm" name="id2554318"></a>
165 <a class="indexterm" name="id2554325"></a>
166 The <em class="parameter"><code>xmlsam</code></em> option can be useful for account migration between database
167 backends or backups. Use of this tool allows the data to be edited before migration
168 into another backend format.
169 </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>
170 <a class="indexterm" name="id2554359"></a>
171 <a class="indexterm" name="id2554365"></a>
172 Old Windows clients send plaintext passwords over the wire. Samba can check these
173 passwords by encrypting them and comparing them to the hash stored in the UNIX user database.
175 <a class="indexterm" name="id2554379"></a>
176 <a class="indexterm" name="id2554386"></a>
177 <a class="indexterm" name="id2554392"></a>
178 <a class="indexterm" name="id2554399"></a>
179 Newer Windows clients send encrypted passwords (LanMan and NT hashes) instead of plaintext passwords over
180 the wire. The newest clients will send only encrypted passwords and refuse to send plaintext passwords unless
181 their registry is tweaked.
183 <a class="indexterm" name="id2554414"></a>
184 <a class="indexterm" name="id2554421"></a>
185 Many people ask why Samba cannot simply use the UNIX password database. Windows requires
186 passwords that are encrypted in its own format. The UNIX passwords can't be converted to
187 UNIX-style encrypted passwords. Because of that, you can't use the standard UNIX user
188 database, and you have to store the LanMan and NT hashes somewhere else.
190 <a class="indexterm" name="id2554437"></a>
191 <a class="indexterm" name="id2554444"></a>
192 <a class="indexterm" name="id2554451"></a>
193 <a class="indexterm" name="id2554458"></a>
194 In addition to differently encrypted passwords, Windows also stores certain data for each
195 user that is not stored in a UNIX user database: for example, workstations the user may logon from,
196 the location where the user's profile is stored, and so on. Samba retrieves and stores this
197 information using a <a class="indexterm" name="id2554470"></a>passdb backend. Commonly available backends are LDAP,
198 tdbsam, plain text file, and MySQL. For more information, see the man page for <code class="filename">smb.conf</code> regarding the
199 <a class="indexterm" name="id2554485"></a>passdb backend parameter.
200 </p><div class="figure"><a name="idmap-sid2uid"></a><p class="title"><b>Figure 10.1. IDMAP: Resolution of SIDs to UIDs.</b></p><div class="mediaobject"><img src="images/idmap-sid2uid.png" width="216" alt="IDMAP: Resolution of SIDs to UIDs."></div></div><p>
201 <a class="indexterm" name="id2554538"></a>
202 <a class="indexterm" name="id2554545"></a>
203 <a class="indexterm" name="id2554551"></a>
204 The resolution of SIDs to UIDs is fundamental to correct operation of Samba. In both cases shown, if winbindd
205 is not running or cannot be contacted, then only local SID/UID resolution is possible. See <a href="passdb.html#idmap-sid2uid" title="Figure 10.1. IDMAP: Resolution of SIDs to UIDs.">resolution of SIDs to UIDs</a> and <a href="passdb.html#idmap-uid2sid" title="Figure 10.2. IDMAP: Resolution of UIDs to SIDs.">resolution of UIDs
206 to SIDs</a> diagrams.
207 </p><div class="figure"><a name="idmap-uid2sid"></a><p class="title"><b>Figure 10.2. IDMAP: Resolution of UIDs to SIDs.</b></p><div class="mediaobject"><img src="images/idmap-uid2sid.png" width="270" alt="IDMAP: Resolution of UIDs to SIDs."></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2554621"></a>Important Notes About Security</h3></div></div></div><p>
208 <a class="indexterm" name="id2554629"></a>
209 <a class="indexterm" name="id2554636"></a>
210 <a class="indexterm" name="id2554643"></a>
211 <a class="indexterm" name="id2554650"></a>
212 <a class="indexterm" name="id2554657"></a>
213 <a class="indexterm" name="id2554664"></a>
214 The UNIX and SMB password encryption techniques seem similar on the surface. This
215 similarity is, however, only skin deep. The UNIX scheme typically sends clear-text
216 passwords over the network when logging in. This is bad. The SMB encryption scheme
217 never sends the clear-text password over the network, but it does store the 16-byte
218 hashed values on disk. This is also bad. Why? Because the 16 byte hashed values
219 are a “<span class="quote">password equivalent.</span>” You cannot derive the user's password from them, but
220 they could potentially be used in a modified client to gain access to a server.
221 This would require considerable technical knowledge on behalf of the attacker but
222 is perfectly possible. You should therefore treat the data stored in whatever passdb
223 backend you use (smbpasswd file, LDAP, MYSQL) as though it contained the clear-text
224 passwords of all your users. Its contents must be kept secret, and the file should
225 be protected accordingly.
227 <a class="indexterm" name="id2554694"></a>
228 <a class="indexterm" name="id2554700"></a>
229 <a class="indexterm" name="id2554707"></a>
230 Ideally, we would like a password scheme that involves neither plaintext passwords
231 on the network nor plaintext passwords on disk. Unfortunately, this is not available because Samba is stuck with
232 having to be compatible with other SMB systems (Windows NT, Windows for Workgroups, Windows 9x/Me).
234 <a class="indexterm" name="id2554722"></a>
235 <a class="indexterm" name="id2554729"></a>
236 Windows NT 4.0 Service Pack 3 changed the default setting so plaintext passwords
237 are disabled from being sent over the wire. This mandates either the use of encrypted
238 password support or editing the Windows NT registry to re-enable plaintext passwords.
240 <a class="indexterm" name="id2554744"></a>
241 <a class="indexterm" name="id2554751"></a>
242 The following versions of Microsoft Windows do not support full domain security protocols,
243 although they may log onto a domain environment:
244 </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>
245 <a class="indexterm" name="id2554789"></a>
246 <a class="indexterm" name="id2554796"></a>
247 <a class="indexterm" name="id2554803"></a>
248 MS Windows XP Home does not have facilities to become a domain member, and it cannot participate in domain logons.
250 The following versions of MS Windows fully support domain security protocols.
251 </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>
252 <a class="indexterm" name="id2554848"></a>
253 <a class="indexterm" name="id2554855"></a>
254 <a class="indexterm" name="id2554862"></a>
255 <a class="indexterm" name="id2554869"></a>
256 <a class="indexterm" name="id2554876"></a>
257 <a class="indexterm" name="id2554883"></a>
258 All current releases of Microsoft SMB/CIFS clients support authentication via the
259 SMB challenge/response mechanism described here. Enabling clear-text authentication
260 does not disable the ability of the client to participate in encrypted authentication.
261 Instead, it allows the client to negotiate either plaintext or encrypted password
264 <a class="indexterm" name="id2554899"></a>
265 <a class="indexterm" name="id2554906"></a>
266 <a class="indexterm" name="id2554913"></a>
267 <a class="indexterm" name="id2554920"></a>
268 <a class="indexterm" name="id2554927"></a>
269 MS Windows clients will cache the encrypted password alone. Where plaintext passwords
270 are re-enabled through the appropriate registry change, the plaintext password is never
271 cached. This means that in the event that a network connections should become disconnected
272 (broken), only the cached (encrypted) password will be sent to the resource server to
273 effect an auto-reconnect. If the resource server does not support encrypted passwords, the
274 auto-reconnect will fail. Use of encrypted passwords is strongly advised.
275 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2554944"></a>Advantages of Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
276 <a class="indexterm" name="id2554955"></a>
277 <a class="indexterm" name="id2554962"></a>
278 <a class="indexterm" name="id2554969"></a>
279 Plaintext passwords are not passed across the network. Someone using a network sniffer
280 cannot just record passwords going to the SMB server.
282 <a class="indexterm" name="id2554983"></a>
283 <a class="indexterm" name="id2554990"></a>
284 <a class="indexterm" name="id2554996"></a>
285 Plaintext passwords are not stored anywhere in memory or on disk.
287 <a class="indexterm" name="id2555009"></a>
288 <a class="indexterm" name="id2555016"></a>
289 <a class="indexterm" name="id2555023"></a>
290 <a class="indexterm" name="id2555030"></a>
291 Windows NT does not like talking to a server that does not support encrypted passwords. It will refuse to
292 browse the server if the server is also in user-level security mode. It will insist on prompting the user for
293 the password on each connection, which is very annoying. The only thing you can do to stop this is to use SMB
296 <a class="indexterm" name="id2555047"></a>
297 <a class="indexterm" name="id2555054"></a>
298 Encrypted password support allows automatic share (resource) reconnects.
300 <a class="indexterm" name="id2555067"></a>
301 <a class="indexterm" name="id2555073"></a>
302 Encrypted passwords are essential for PDC/BDC operation.
303 </p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555084"></a>Advantages of Non-Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
304 <a class="indexterm" name="id2555096"></a>
305 Plaintext passwords are not kept on disk and are not cached in memory.
307 <a class="indexterm" name="id2555108"></a>
308 <a class="indexterm" name="id2555115"></a>
309 Plaintext passwords use the same password file as other UNIX services, such as Login and FTP.
311 <a class="indexterm" name="id2555128"></a>
312 <a class="indexterm" name="id2555135"></a>
313 Use of other services (such as Telnet and FTP) that send plaintext passwords over
314 the network makes sending them for SMB not such a big deal.
315 </p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555148"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div></div><p>
316 <a class="indexterm" name="id2555157"></a>
317 <a class="indexterm" name="id2555163"></a>
318 <a class="indexterm" name="id2555170"></a>
319 Every operation in UNIX/Linux requires a user identifier (UID), just as in
320 MS Windows NT4/200x this requires a security identifier (SID). Samba provides
321 two means for mapping an MS Windows user to a UNIX/Linux UID.
323 <a class="indexterm" name="id2555184"></a>
324 <a class="indexterm" name="id2555190"></a>
325 <a class="indexterm" name="id2555197"></a>
326 <a class="indexterm" name="id2555203"></a>
327 <a class="indexterm" name="id2555211"></a>
328 First, all Samba SAM database accounts require a UNIX/Linux UID that the account will map to. As users are
329 added to the account information database, Samba will call the <a class="indexterm" name="id2555221"></a>add user script
330 interface to add the account to the Samba host OS. In essence all accounts in the local SAM require a local
333 <a class="indexterm" name="id2555233"></a>
334 <a class="indexterm" name="id2555240"></a>
335 <a class="indexterm" name="id2555247"></a>
336 <a class="indexterm" name="id2555253"></a>
337 <a class="indexterm" name="id2555260"></a>
338 <a class="indexterm" name="id2555267"></a>
339 <a class="indexterm" name="id2555274"></a>
340 The second way to map Windows SID to UNIX UID is via the <span class="emphasis"><em>idmap uid</em></span> and
341 <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
342 these parameters. These parameters are essential when mapping users from a remote (non-member Windows client
343 or a member of a foreign domain) SAM server.
344 </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>
345 <a class="indexterm" name="id2555313"></a>
346 <a class="indexterm" name="id2555320"></a>
347 <a class="indexterm" name="id2555326"></a>
348 <a class="indexterm" name="id2555333"></a>
349 <a class="indexterm" name="id2555340"></a>
350 <a class="indexterm" name="id2555346"></a>
351 Samba-3 has a special facility that makes it possible to maintain identical UIDs and GIDs
352 on all servers in a distributed network. A distributed network is one where there exists
353 a PDC, one or more BDCs, and/or one or more domain member servers. Why is this important?
354 This is important if files are being shared over more than one protocol (e.g., NFS) and where
355 users are copying files across UNIX/Linux systems using tools such as <span><strong class="command">rsync</strong></span>.
357 <a class="indexterm" name="id2555370"></a>
358 <a class="indexterm" name="id2555376"></a>
359 <a class="indexterm" name="id2555383"></a>
360 <a class="indexterm" name="id2555390"></a>
361 <a class="indexterm" name="id2555396"></a>
362 <a class="indexterm" name="id2555403"></a>
363 <a class="indexterm" name="id2555410"></a>
364 <a class="indexterm" name="id2555417"></a>
365 The special facility is enabled using a parameter called <em class="parameter"><code>idmap backend</code></em>.
366 The default setting for this parameter is an empty string. Technically it is possible to use
367 an LDAP-based idmap backend for UIDs and GIDs, but it makes most sense when this is done for
368 network configurations that also use LDAP for the SAM backend.
369 <a href="passdb.html#idmapbackendexample" title="Example 10.1. Example Configuration with the LDAP idmap Backend">Example Configuration with the LDAP idmap Backend</a>
370 shows that configuration.
371 </p><a class="indexterm" name="id2555446"></a><div class="example"><a name="idmapbackendexample"></a><p class="title"><b>Example 10.1. Example Configuration with the LDAP idmap Backend</b></p><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="id2555480"></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="id2555497"></a><em class="parameter"><code>idmap backend = ldap:ldaps://ldap-server.quenya.org</code></em></td></tr></table></div><p>
372 <a class="indexterm" name="id2555514"></a>
373 <a class="indexterm" name="id2555520"></a>
374 A network administrator who wants to make significant use of LDAP backends will sooner or later be
375 exposed to the excellent work done by PADL Software. PADL <a href="http://www.padl.com" target="_top">http://www.padl.com</a> have
376 produced and released to open source an array of tools that might be of interest. These tools include:
377 </p><div class="itemizedlist"><ul type="disc"><li><p>
378 <a class="indexterm" name="id2555544"></a>
379 <a class="indexterm" name="id2555551"></a>
380 <a class="indexterm" name="id2555558"></a>
381 <a class="indexterm" name="id2555564"></a>
382 <a class="indexterm" name="id2555571"></a>
383 <a class="indexterm" name="id2555578"></a>
384 <a class="indexterm" name="id2555584"></a>
385 <a class="indexterm" name="id2555591"></a>
386 <span class="emphasis"><em>nss_ldap:</em></span> An LDAP name service switch (NSS) module to provide native
387 name service support for AIX, Linux, Solaris, and other operating systems. This tool
388 can be used for centralized storage and retrieval of UIDs and GIDs.
390 <a class="indexterm" name="id2555611"></a>
391 <a class="indexterm" name="id2555618"></a>
392 <a class="indexterm" name="id2555624"></a>
393 <a class="indexterm" name="id2555631"></a>
394 <span class="emphasis"><em>pam_ldap:</em></span> A PAM module that provides LDAP integration for UNIX/Linux
395 system access authentication.
397 <a class="indexterm" name="id2555650"></a>
398 <a class="indexterm" name="id2555657"></a>
399 <a class="indexterm" name="id2555664"></a>
400 <a class="indexterm" name="id2555670"></a>
401 <span class="emphasis"><em>idmap_ad:</em></span> An IDMAP backend that supports the Microsoft Services for
402 UNIX RFC 2307 schema available from the PADL Web
403 <a href="http://www.padl.com/download/xad_oss_plugins.tar.gz" target="_top">site</a>.
404 </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2555694"></a>Comments Regarding LDAP</h3></div></div></div><p>
405 <a class="indexterm" name="id2555702"></a>
406 <a class="indexterm" name="id2555711"></a>
407 <a class="indexterm" name="id2555718"></a>
408 <a class="indexterm" name="id2555724"></a>
409 There is much excitement and interest in LDAP directories in the information technology world
410 today. The LDAP architecture was designed to be highly scalable. It was also designed for
411 use across a huge number of potential areas of application encompassing a wide range of operating
412 systems and platforms. LDAP technologies are at the heart of the current generations of Federated
413 Identity Management (FIM) solutions that can underlie a corporate Single Sign-On (SSO) environment.
415 <a class="indexterm" name="id2555742"></a>
416 <a class="indexterm" name="id2555749"></a>
417 <a class="indexterm" name="id2555756"></a>
418 <a class="indexterm" name="id2555762"></a>
419 LDAP implementations have been built across a wide variety of platforms. It lies at the core of Microsoft
420 Windows Active Directory services (ADS), Novell's eDirectory, as well as many others. Implementation of the
421 directory services LDAP involves interaction with legacy as well as new generation applications, all of which
422 depend on some form of authentication services.
424 <a class="indexterm" name="id2555779"></a>
425 <a class="indexterm" name="id2555786"></a>
426 <a class="indexterm" name="id2555793"></a>
427 <a class="indexterm" name="id2555800"></a>
428 <a class="indexterm" name="id2555807"></a>
429 <a class="indexterm" name="id2555814"></a>
430 <a class="indexterm" name="id2555820"></a>
431 <a class="indexterm" name="id2555827"></a>
432 <a class="indexterm" name="id2555834"></a>
433 <a class="indexterm" name="id2555841"></a>
434 <a class="indexterm" name="id2555848"></a>
435 <a class="indexterm" name="id2555855"></a>
436 <a class="indexterm" name="id2555862"></a>
437 <a class="indexterm" name="id2555869"></a>
438 UNIX services can utilize LDAP directory information for authentication and access controls
439 through intermediate tools and utilities. The total environment that consists of the LDAP directory
440 and the middle-ware tools and utilities makes it possible for all user access to the UNIX platform
441 to be managed from a central environment and yet distributed to wherever the point of need may
442 be physically located. Applications that benefit from this infrastructure include: UNIX login
443 shells, mail and messaging systems, quota controls, printing systems, DNS servers, DHCP servers,
446 <a class="indexterm" name="id2555889"></a>
447 <a class="indexterm" name="id2555896"></a>
448 <a class="indexterm" name="id2555903"></a>
449 <a class="indexterm" name="id2555910"></a>
450 <a class="indexterm" name="id2555916"></a>
451 <a class="indexterm" name="id2555923"></a>
452 Many sites are installing LDAP for the first time in order to provide a scalable passdb backend
453 for Samba. Others are faced with the need to adapt an existing LDAP directory to new uses such
454 as for the Samba SAM backend. Whatever your particular need and attraction to Samba may be,
455 decisions made in respect of the design of the LDAP directory structure and its implementation
456 are of a durable nature for the site. These have far-reaching implications that affect long-term
457 information systems management costs.
459 <a class="indexterm" name="id2555942"></a>
460 <a class="indexterm" name="id2555949"></a>
461 Do not rush into an LDAP deployment. Take the time to understand how the design of the Directory
462 Information Tree (DIT) may impact current and future site needs, as well as the ability to meet
463 them. The way that Samba SAM information should be stored within the DIT varies from site to site
464 and with each implementation new experience is gained. It is well understood by LDAP veterans that
465 first implementations create awakening, second implementations of LDAP create fear, and
466 third-generation deployments bring peace and tranquility.
467 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2555969"></a>Caution Regarding LDAP and Samba</h4></div></div></div><p>
468 <a class="indexterm" name="id2555977"></a>
469 <a class="indexterm" name="id2555984"></a>
470 <a class="indexterm" name="id2555991"></a>
471 <a class="indexterm" name="id2555998"></a>
472 <a class="indexterm" name="id2556005"></a>
473 <a class="indexterm" name="id2556012"></a>
474 <a class="indexterm" name="id2556019"></a>
475 Samba requires UNIX POSIX identity information as well as a place to store information that is
476 specific to Samba and the Windows networking environment. The most used information that must
477 be dealt with includes: user accounts, group accounts, machine trust accounts, interdomain
478 trust accounts, and intermediate information specific to Samba internals.
480 <a class="indexterm" name="id2556035"></a>
481 <a class="indexterm" name="id2556042"></a>
482 <a class="indexterm" name="id2556049"></a>
483 The example deployment guidelines in this book, as well as other books and HOWTO documents
484 available from the internet may not fit with established directory designs and implementations.
485 The existing DIT may not be able to accommodate the simple information layout proposed in common
486 sources. Additionally, you may find that the common scripts and tools that are used to provision
487 the LDAP directory for use with Samba may not suit your needs.
489 <a class="indexterm" name="id2556067"></a>
490 It is not uncommon, for sites that have existing LDAP DITs to find necessity to generate a
491 set of site-specific scripts and utilities to make it possible to deploy Samba within the
492 scope of site operations. The way that user and group accounts are distributed throughout
493 the DIT may make this a challenging matter. The solution will, of course, be rewarding, but
494 the journey to it may be challenging. Take time to understand site needs and do not rush
497 <a class="indexterm" name="id2556085"></a>
498 <a class="indexterm" name="id2556092"></a>
499 Above all, do not blindly use scripts and tools that are not suitable for your site. Check
500 and validate all scripts before you execute them to make sure that the existing infrastructure
501 will not be damaged by inadvertent use of an inappropriate tool.
502 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556106"></a>LDAP Directories and Windows Computer Accounts</h3></div></div></div><p>
503 <a class="indexterm" name="id2556115"></a>
504 <a class="indexterm" name="id2556122"></a>
505 <a class="indexterm" name="id2556128"></a>
506 Samba doesn't provide a turnkey solution to LDAP. It is best to deal with the design and
507 configuration of an LDAP directory prior to integration with Samba. A working knowledge
508 of LDAP makes Samba integration easy, and the lack of a working knowledge of LDAP can make
509 it a frustrating experience.
511 <a class="indexterm" name="id2556144"></a>
512 <a class="indexterm" name="id2556151"></a>
513 <a class="indexterm" name="id2556158"></a>
514 Computer (machine) accounts can be placed wherever you like in an LDAP directory subject
515 to some constraints that are described in this chapter.
517 <a class="indexterm" name="id2556170"></a>
518 <a class="indexterm" name="id2556177"></a>
519 <a class="indexterm" name="id2556184"></a>
520 <a class="indexterm" name="id2556191"></a>
521 <a class="indexterm" name="id2556198"></a>
522 <a class="indexterm" name="id2556205"></a>
523 <a class="indexterm" name="id2556212"></a>
524 The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba.
525 Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats
526 them. A user account and a machine account are indistinquishable from each other, except that
527 the machine account ends in a $ character, as do trust accounts.
529 <a class="indexterm" name="id2556228"></a>
530 <a class="indexterm" name="id2556235"></a>
531 <a class="indexterm" name="id2556242"></a>
532 <a class="indexterm" name="id2556249"></a>
533 <a class="indexterm" name="id2556255"></a>
534 The need for Windows user, group, machine, trust, and other accounts to be tied to a valid UNIX
535 UID is a design decision that was made a long way back in the history of Samba development. It
536 is unlikely that this decision will be reversed or changed during the remaining life of the
539 <a class="indexterm" name="id2556270"></a>
540 <a class="indexterm" name="id2556277"></a>
541 <a class="indexterm" name="id2556284"></a>
542 The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that
543 must refer back to the host operating system on which Samba is running. The NSS is the preferred
544 mechanism that shields applications (like Samba) from the need to know everything about every
547 <a class="indexterm" name="id2556299"></a>
548 <a class="indexterm" name="id2556305"></a>
549 <a class="indexterm" name="id2556312"></a>
550 <a class="indexterm" name="id2556319"></a>
551 <a class="indexterm" name="id2556326"></a>
552 <a class="indexterm" name="id2556332"></a>
553 <a class="indexterm" name="id2556339"></a>
554 Samba asks the host OS to provide a UID via the “<span class="quote">passwd</span>”, “<span class="quote">shadow</span>”,
555 and “<span class="quote">group</span>” facilities in the NSS control (configuration) file. The best tool
556 for achieving this is left up to the UNIX administrator to determine. It is not imposed by
557 Samba. Samba provides winbindd with its support libraries as one method. It is
558 possible to do this via LDAP, and for that Samba provides the appropriate hooks so that
559 all account entities can be located in an LDAP directory.
561 <a class="indexterm" name="id2556367"></a>
562 <a class="indexterm" name="id2556374"></a>
563 <a class="indexterm" name="id2556381"></a>
564 <a class="indexterm" name="id2556387"></a>
565 <a class="indexterm" name="id2556394"></a>
566 For many the weapon of choice is to use the PADL nss_ldap utility. This utility must
567 be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That
568 is fundamentally an LDAP design question. The information provided on the Samba list and
569 in the documentation is directed at providing working examples only. The design
570 of an LDAP directory is a complex subject that is beyond the scope of this documentation.
571 </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>
572 <a class="indexterm" name="id2556425"></a>
573 <a class="indexterm" name="id2556431"></a>
574 <a class="indexterm" name="id2556438"></a>
575 Samba provides two tools for management of user and machine accounts:
576 <span><strong class="command">smbpasswd</strong></span> and <span><strong class="command">pdbedit</strong></span>.
578 <a class="indexterm" name="id2556461"></a>
579 <a class="indexterm" name="id2556468"></a>
580 <a class="indexterm" name="id2556475"></a>
581 The <span><strong class="command">pdbedit</strong></span> can be used to manage account policies in addition to
582 Samba user account information. The policy management capability is used to administer
583 domain default settings for password aging and management controls to handle failed login
586 <a class="indexterm" name="id2556495"></a>
587 <a class="indexterm" name="id2556502"></a>
588 <a class="indexterm" name="id2556509"></a>
589 <a class="indexterm" name="id2556516"></a>
590 Some people are confused when reference is made to <code class="literal">smbpasswd</code> because the
591 name refers to a storage mechanism for SambaSAMAccount information, but it is also the name
592 of a utility tool. That tool is destined to eventually be replaced by new functionality that
593 is being added to the <span><strong class="command">net</strong></span> toolset (see <a href="NetCommand.html" title="Chapter 12. Remote and Local Management: The Net Command">the Net Command</a>.
594 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2556547"></a>The <span><strong class="command">smbpasswd</strong></span> Tool</h3></div></div></div><p>
595 <a class="indexterm" name="id2556560"></a>
596 <a class="indexterm" name="id2556567"></a>
597 <a class="indexterm" name="id2556574"></a>
598 <a class="indexterm" name="id2556581"></a>
599 <a class="indexterm" name="id2556588"></a>
600 The <span><strong class="command">smbpasswd</strong></span> utility is similar to the <span><strong class="command">passwd</strong></span>
601 and <span><strong class="command">yppasswd</strong></span> programs. It maintains the two 32 byte password
602 fields in the passdb backend. This utility operates independently of the actual
603 account and password storage methods used (as specified by the <em class="parameter"><code>passdb
604 backend</code></em> in the <code class="filename">smb.conf</code> file.
606 <a class="indexterm" name="id2556632"></a>
607 <a class="indexterm" name="id2556639"></a>
608 <span><strong class="command">smbpasswd</strong></span> works in a client-server mode where it contacts the
609 local smbd to change the user's password on its behalf. This has enormous benefits.
611 <a class="indexterm" name="id2556657"></a>
612 <a class="indexterm" name="id2556664"></a>
613 <span><strong class="command">smbpasswd</strong></span> has the capability to change passwords on Windows NT
614 servers (this only works when the request is sent to the NT PDC if changing an NT
615 domain user's password).
617 <a class="indexterm" name="id2556683"></a>
618 <a class="indexterm" name="id2556690"></a>
619 <span><strong class="command">smbpasswd</strong></span> can be used to:
620 </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>
621 To run smbpasswd as a normal user, just type:
623 </p><pre class="screen">
624 <code class="prompt">$ </code><strong class="userinput"><code>smbpasswd</code></strong>
625 <code class="prompt">Old SMB password: </code><strong class="userinput"><code><em class="replaceable"><code>secret</code></em></code></strong>
627 For <em class="replaceable"><code>secret</code></em>, type the old value here or press return if
628 there is no old password.
629 </p><pre class="screen">
630 <code class="prompt">New SMB Password: </code><strong class="userinput"><code><em class="replaceable"><code>new secret</code></em></code></strong>
631 <code class="prompt">Repeat New SMB Password: </code><strong class="userinput"><code><em class="replaceable"><code>new secret</code></em></code></strong>
634 If the old value does not match the current value stored for that user, or the two
635 new values do not match each other, then the password will not be changed.
637 <a class="indexterm" name="id2556829"></a>
638 When invoked by an ordinary user, the command will allow only the user to change his or her own
641 <a class="indexterm" name="id2556842"></a>
642 <a class="indexterm" name="id2556848"></a>
643 When run by root, <span><strong class="command">smbpasswd</strong></span> may take an optional argument specifying
644 the username whose SMB password you wish to change. When run as root, <span><strong class="command">smbpasswd</strong></span>
645 does not prompt for or check the old password value, thus allowing root to set passwords
646 for users who have forgotten their passwords.
648 <a class="indexterm" name="id2556875"></a>
649 <a class="indexterm" name="id2556882"></a>
650 <a class="indexterm" name="id2556889"></a>
651 <a class="indexterm" name="id2556895"></a>
652 <span><strong class="command">smbpasswd</strong></span> is designed to work in the way familiar to UNIX
653 users who use the <span><strong class="command">passwd</strong></span> or <span><strong class="command">yppasswd</strong></span> commands.
654 While designed for administrative use, this tool provides essential user-level
655 password change capabilities.
657 <a class="indexterm" name="id2556927"></a>
658 For more details on using <span><strong class="command">smbpasswd</strong></span>, refer to the man page (the
659 definitive reference).
660 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="pdbeditthing"></a>The <span><strong class="command">pdbedit</strong></span> Tool</h3></div></div></div><p>
661 <a class="indexterm" name="id2556961"></a>
662 <a class="indexterm" name="id2556968"></a>
663 <a class="indexterm" name="id2556975"></a>
664 <a class="indexterm" name="id2556982"></a>
665 <span><strong class="command">pdbedit</strong></span> is a tool that can be used only by root. It is used to
666 manage the passdb backend, as well as domain-wide account policy settings. <span><strong class="command">pdbedit</strong></span>
668 </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>
669 <a class="indexterm" name="id2557041"></a>
670 Under the terms of the Sarbanes-Oxley Act of 2002, American businesses and organizations are mandated to
671 implement a series of <code class="literal">internal controls</code> and procedures to communicate, store,
672 and protect financial data. The Sarbanes-Oxley Act has far reaching implications in respect of:
673 </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
674 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>
675 <a class="indexterm" name="id2557113"></a>
676 <a class="indexterm" name="id2557120"></a>
677 In short, the Sarbanes-Oxley Act of 2002 is an instrument that enforces accountability in respect of
678 business related information systems so as to ensure the compliance of all information systems that
679 are used to store personal information and particularly for financial records processing. Similar
680 accountabilities are being demanded around the world.
682 <a class="indexterm" name="id2557137"></a>
683 <a class="indexterm" name="id2557143"></a>
684 <a class="indexterm" name="id2557150"></a>
685 <a class="indexterm" name="id2557157"></a>
686 <a class="indexterm" name="id2557164"></a>
687 The need to be familiar with the Samba tools and facilities that permit information systems operation
688 in compliance with government laws and regulations is clear to all. The <span><strong class="command">pdbedit</strong></span> is
689 currently the only Samba tool that provides the capacity to manage account and systems access controls
690 and policies. During the remaining life-cycle of the Samba-3 series it is possible the new tools may
691 be implemented to aid in this important area.
693 Domain global policy controls available in Windows NT4 compared with Samba
694 is shown in <a href="passdb.html#policycontrols" title="Table 10.1. NT4 Domain v's Samba Policy Controls">NT4 Domain v's Samba Policy Controls</a>.
695 </p><div class="table"><a name="policycontrols"></a><p class="title"><b>Table 10.1. NT4 Domain v's Samba Policy Controls</b></p><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><p>
696 <a class="indexterm" name="id2557546"></a>
697 <a class="indexterm" name="id2557553"></a>
698 <a class="indexterm" name="id2557560"></a>
699 <a class="indexterm" name="id2557566"></a>
700 The <span><strong class="command">pdbedit</strong></span> tool is the only one that can manage the account
701 security and policy settings. It is capable of all operations that smbpasswd can
702 do as well as a superset of them.
704 <a class="indexterm" name="id2557585"></a>
705 <a class="indexterm" name="id2557592"></a>
706 <a class="indexterm" name="id2557599"></a>
707 One particularly important purpose of the <span><strong class="command">pdbedit</strong></span> is to allow
708 the migration of account information from one passdb backend to another. See the
709 <a href="passdb.html#XMLpassdb" title="XML">XML</a> password backend section of this chapter.
710 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2557624"></a>User Account Management</h4></div></div></div><p>
711 <a class="indexterm" name="id2557632"></a>
712 <a class="indexterm" name="id2557639"></a>
713 <a class="indexterm" name="id2557645"></a>
714 <a class="indexterm" name="id2557652"></a>
715 <a class="indexterm" name="id2557659"></a>
716 <a class="indexterm" name="id2557666"></a>
717 <a class="indexterm" name="id2557673"></a>
718 The <span><strong class="command">pdbedit</strong></span> tool, like the <span><strong class="command">smbpasswd</strong></span> tool, requires
719 that a POSIX user account already exists in the UNIX/Linux system accounts database (backend).
720 Neither tool will call out to the operating system to create a user account because this is
721 considered to be the responsibility of the system administrator. When the Windows NT4 domain
722 user manager is used to add an account, Samba will implement the <code class="literal">add user script</code>
723 (as well as the other interface scripts) to ensure that user, group and machine accounts are
724 correctly created and changed. The use of the <span><strong class="command">pdbedit</strong></span> tool does not
725 make use of these interface scripts.
727 <a class="indexterm" name="id2557717"></a>
728 <a class="indexterm" name="id2557724"></a>
729 Before attempting to use the <span><strong class="command">pdbedit</strong></span> tool to manage user and machine
730 accounts, make certain that a system (POSIX) account has already been created.
731 </p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2557740"></a>Listing User and Machine Accounts</h5></div></div></div><p>
732 <a class="indexterm" name="id2557748"></a>
733 <a class="indexterm" name="id2557755"></a>
734 The following is an example of the user account information that is stored in
735 a tdbsam password backend. This listing was produced by running:
736 </p><pre class="screen">
737 <code class="prompt">$ </code><strong class="userinput"><code>pdbedit -Lv met</code></strong>
741 User SID: S-1-5-21-1449123459-1407424037-3116680435-2004
742 Primary Group SID: S-1-5-21-1449123459-1407424037-3116680435-1201
743 Full Name: Melissa E Terpstra
744 Home Directory: \\frodo\met\Win9Profile
746 Logon Script: scripts\logon.bat
747 Profile Path: \\frodo\Profiles\met
750 Workstations: melbelle
753 Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
754 Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT
755 Password last set: Sat, 14 Dec 2002 14:37:03 GMT
756 Password can change: Sat, 14 Dec 2002 14:37:03 GMT
757 Password must change: Mon, 18 Jan 2038 20:14:07 GMT
760 <a class="indexterm" name="id2557797"></a>
761 Accounts can also be listed in the older <code class="literal">smbpasswd</code> format:
762 </p><pre class="screen">
763 <code class="prompt">root# </code><strong class="userinput"><code>pdbedit -Lw</code></strong>
764 root:0:84B0D8E14D158FF8417EAF50CFAC29C3:
765 AF6DD3FD4E2EA8BDE1695A3F05EFBF52:[U ]:LCT-42681AB8:
766 jht:1000:6BBC4159020A52741486235A2333E4D2:
767 CC099521AD554A3C3CF2556274DBCFBC:[U ]:LCT-40D75B5B:
768 rcg:1002:E95D4331A6F23AF8AAD3B435B51404EE:
769 BB0F2C39B04CA6100F0E535DF8314B43:[U ]:LCT-40D7C5A3:
770 afw:1003:1AAFA7F9F6DC1DEAAAD3B435B51404EE:
771 CE92C2F9471594CDC4E7860CA6BC62DB:[T ]:LCT-40DA501F:
772 met:1004:A2848CB7E076B435AAD3B435B51404EE:
773 F25F5D3405085C555236B80B7B22C0D2:[U ]:LCT-4244FAB8:
774 aurora$:1005:060DE593EA638B8ACC4A19F14D2FF2BB:
775 060DE593EA638B8ACC4A19F14D2FF2BB:[W ]:LCT-4173E5CC:
776 temptation$:1006:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
777 A96703C014E404E33D4049F706C45EE9:[W ]:LCT-42BF0C57:
778 vaioboss$:1001:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
779 88A30A095160072784C88F811E89F98A:[W ]:LCT-41C3878D:
780 frodo$:1008:15891DC6B843ECA41249940C814E316B:
781 B68EADCCD18E17503D3DAD3E6B0B9A75:[W ]:LCT-42B7979F:
782 marvel$:1011:BF709959C3C94E0B3958B7B84A3BB6F3:
783 C610EFE9A385A3E8AA46ADFD576E6881:[W ]:LCT-40F07A4
785 <a class="indexterm" name="id2557846"></a>
786 <a class="indexterm" name="id2557852"></a>
787 <a class="indexterm" name="id2557859"></a>
788 <a class="indexterm" name="id2557866"></a>
789 <a class="indexterm" name="id2557873"></a>
790 <a class="indexterm" name="id2557880"></a>
791 The account information that was returned by this command in order from left to right
792 consists of the following colon separated data:
793 </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>
794 <a class="indexterm" name="id2557930"></a>
795 <a class="indexterm" name="id2557937"></a>
796 The Account Flags parameters are documented in the <span><strong class="command">pdbedit</strong></span> man page, and are
797 briefly documented in <a href="passdb.html#TOSHARG-acctflags" title="Account Flags Management">the Account Flags Management section</a>.
799 <a class="indexterm" name="id2557964"></a>
800 The LCT data consists of 8 hexadecimal characters representing the time since January 1, 1970, of
801 the time when the password was last changed.
802 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2557975"></a>Adding User Accounts</h5></div></div></div><p>
803 <a class="indexterm" name="id2557983"></a>
804 <a class="indexterm" name="id2557990"></a>
805 <a class="indexterm" name="id2557997"></a>
806 <a class="indexterm" name="id2558004"></a>
807 <a class="indexterm" name="id2558010"></a>
808 The <span><strong class="command">pdbedit</strong></span> can be used to add a user account to a standalone server
809 or to a domain. In the example shown here the account for the user <code class="literal">vlaan</code>
810 has been created before attempting to add the SambaSAMAccount.
811 </p><pre class="screen">
812 <code class="prompt">root# </code> pdbedit -a vlaan
813 new password: secretpw
814 retype new password: secretpw
818 User SID: S-1-5-21-726309263-4128913605-1168186429-3014
819 Primary Group SID: S-1-5-21-726309263-4128913605-1168186429-513
820 Full Name: Victor Laan
821 Home Directory: \\frodo\vlaan
823 Logon Script: scripts\logon.bat
824 Profile Path: \\frodo\profiles\vlaan
826 Account desc: Guest User
830 Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
831 Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT
832 Password last set: Wed, 29 Jun 2005 19:35:12 GMT
833 Password can change: Wed, 29 Jun 2005 19:35:12 GMT
834 Password must change: Mon, 18 Jan 2038 20:14:07 GMT
835 Last bad password : 0
836 Bad password count : 0
837 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
839 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2558062"></a>Deleting Accounts</h5></div></div></div><p>
840 <a class="indexterm" name="id2558070"></a>
841 <a class="indexterm" name="id2558077"></a>
842 <a class="indexterm" name="id2558084"></a>
843 <a class="indexterm" name="id2558091"></a>
844 An account can be deleted from the SambaSAMAccount database
845 </p><pre class="screen">
846 <code class="prompt">root# </code> pdbedit -x vlaan
848 The account is removed without further screen output. The account is removed only from the
849 SambaSAMAccount (passdb backend) database, it is not removed from the UNIX account backend.
851 <a class="indexterm" name="id2558117"></a>
852 <a class="indexterm" name="id2558124"></a>
853 The use of the NT4 domain user manager to delete an account will trigger the <em class="parameter"><code>delete user
854 script</code></em>, but not the <span><strong class="command">pdbedit</strong></span> tool.
855 </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2558147"></a>Changing User Accounts</h5></div></div></div><p>
856 <a class="indexterm" name="id2558155"></a>
857 Refer to the <span><strong class="command">pdbedit</strong></span> man page for a full synopsis of all operations
858 that are available with this tool.
860 <a class="indexterm" name="id2558173"></a>
861 An example of a simple change in the user account information is the change of the full name
862 information shown here:
863 </p><pre class="screen">
864 <code class="prompt">root# </code> pdbedit -r --fullname="Victor Aluicious Laan" vlaan
866 Primary Group SID: S-1-5-21-726309263-4128913605-1168186429-513
867 Full Name: Victor Aluicious Laan
868 Home Directory: \\frodo\vlaan
872 <a class="indexterm" name="id2558200"></a>
873 <a class="indexterm" name="id2558206"></a>
874 <a class="indexterm" name="id2558213"></a>
875 Let us assume for a moment that a user's password has expired and the user is unable to
876 change the password at this time. It may be necessary to give the user additional grace time
877 so that it is possible to continue to work with the account and the original password. This
878 demonstrates how the password expiration settings may be updated
879 </p><pre class="screen">
880 <code class="prompt">root# </code> pdbedit -Lv vlaan
882 Password last set: Sun, 09 Sep 2001 22:21:40 GMT
883 Password can change: Thu, 03 Jan 2002 15:08:35 GMT
884 Password must change: Thu, 03 Jan 2002 15:08:35 GMT
885 Last bad password : Thu, 03 Jan 2002 15:08:35 GMT
886 Bad password count : 2
889 <a class="indexterm" name="id2558242"></a>
890 <a class="indexterm" name="id2558249"></a>
891 The user has recorded 2 bad logon attempts and the next will lock the account, but the
892 password is also expired. Here is how this account can be reset:
893 </p><pre class="screen">
894 <code class="prompt">root# </code> pdbedit -z vlaan
896 Password last set: Sun, 09 Sep 2001 22:21:40 GMT
897 Password can change: Thu, 03 Jan 2002 15:08:35 GMT
898 Password must change: Thu, 03 Jan 2002 15:08:35 GMT
899 Last bad password : 0
900 Bad password count : 0
903 The <code class="literal">Password must change:</code> parameter can be reset like this:
904 </p><pre class="screen">
905 <code class="prompt">root# </code> pdbedit --pwd-must-change-time=1200000000 vlaan
907 Password last set: Sun, 09 Sep 2001 22:21:40 GMT
908 Password can change: Thu, 03 Jan 2002 15:08:35 GMT
909 Password must change: Thu, 10 Jan 2008 14:20:00 GMT
912 Another way to use this tools is to set the date like this:
913 </p><pre class="screen">
914 <code class="prompt">root# </code> pdbedit --pwd-must-change-time="2010-01-01" \
915 --time-format="%Y-%m-%d" vlaan
917 Password last set: Sun, 09 Sep 2001 22:21:40 GMT
918 Password can change: Thu, 03 Jan 2002 15:08:35 GMT
919 Password must change: Fri, 01 Jan 2010 00:00:00 GMT
922 <a class="indexterm" name="id2558313"></a>
923 <a class="indexterm" name="id2558320"></a>
924 Refer to the strptime man page for specific time format information.
926 <a class="indexterm" name="id2558331"></a>
927 <a class="indexterm" name="id2558338"></a>
928 Please refer to the pdbedit man page for further information relating to SambaSAMAccount
930 </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>
931 <a class="indexterm" name="id2558360"></a>
932 <a class="indexterm" name="id2558367"></a>
933 <a class="indexterm" name="id2558376"></a>
934 <a class="indexterm" name="id2558382"></a>
935 The Samba SAM account flags are properly called the ACB (account control block) within
936 the Samba source code. In some parts of the Samba source code they are referred to as the
937 account encode_bits, and also as the account control flags.
939 <a class="indexterm" name="id2558397"></a>
940 <a class="indexterm" name="id2558404"></a>
941 <a class="indexterm" name="id2558411"></a>
942 <a class="indexterm" name="id2558418"></a>
943 <a class="indexterm" name="id2558424"></a>
944 The manual adjustment of user, machine (workstation or server) or an inter-domain trust
945 account account flgas should not be necessary under normal conditions of use of Samba. On the other hand,
946 where this information becomes corrupted for some reason, the ability to correct the damaged data is certainly
947 useful. The tool of choice by which such correction can be affected is the <span><strong class="command">pdbedit</strong></span> utility.
949 <a class="indexterm" name="id2558447"></a>
950 <a class="indexterm" name="id2558454"></a>
951 There have been a few requests for information regarding the account flags from developers
952 who are creating their own Samba management tools. An example of a need for information regarding
953 the proper management of the account flags is evident when developing scripts that will be used
954 to manage an LDAP directory.
956 <a class="indexterm" name="id2558470"></a>
957 <a class="indexterm" name="id2558477"></a>
958 The account flag field can contain up to 16 characters. Presently, only 11 are in use.
959 These are listed in <a href="passdb.html#accountflags" title="Table 10.2. Samba SAM Account Control Block Flags">Samba SAM Account Control Block Flags</a>.
960 The order in which the flags are specified to the <span><strong class="command">pdbedit</strong></span> command is not important.
961 In fact, they can be set without problem in any order in the SambaAcctFlags record in the LDAP directory.
962 </p><div class="table"><a name="accountflags"></a><p class="title"><b>Table 10.2. Samba SAM Account Control Block Flags</b></p><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><p>
963 <a class="indexterm" name="id2558705"></a>
964 <a class="indexterm" name="id2558712"></a>
965 An example of use of the <span><strong class="command">pdbedit</strong></span> utility to set the account control flags
967 </p><pre class="screen">
968 <code class="prompt">root# </code> pdbedit -r -c "[DLX]" jra
971 Account Flags: [DHULX ]
972 User SID: S-1-5-21-729263-4123605-1186429-3000
973 Primary Group SID: S-1-5-21-729263-4123605-1186429-513
974 Full Name: John H Terpstra,Utah Office
975 Home Directory: \\aurora\jht
977 Logon Script: scripts\logon.bat
978 Profile Path: \\aurora\profiles\jht
980 Account desc: BluntObject
983 Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
985 Password last set: Sun, 03 Jul 2005 23:19:18 GMT
986 Password can change: Sun, 03 Jul 2005 23:19:18 GMT
987 Password must change: Mon, 18 Jan 2038 20:14:07 GMT
988 Last bad password : 0
989 Bad password count : 0
990 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
992 <a class="indexterm" name="id2558767"></a>
993 The flags can be reset to the default settings by executing:
994 </p><pre class="screen">
995 <code class="prompt">root# </code> pdbedit -r -c "[]" jra
999 User SID: S-1-5-21-729263-4123605-1186429-3000
1000 Primary Group SID: S-1-5-21-729263-4123605-1186429-513
1001 Full Name: John H Terpstra,Utah Office
1002 Home Directory: \\aurora\jht
1004 Logon Script: scripts\logon.bat
1005 Profile Path: \\aurora\profiles\jht
1007 Account desc: BluntObject
1010 Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
1012 Password last set: Sun, 03 Jul 2005 23:19:18 GMT
1013 Password can change: Sun, 03 Jul 2005 23:19:18 GMT
1014 Password must change: Mon, 18 Jan 2038 20:14:07 GMT
1015 Last bad password : 0
1016 Bad password count : 0
1017 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
1019 </p></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2558804"></a>Domain Account Policy Managment</h5></div></div></div><p>
1020 <a class="indexterm" name="id2558812"></a>
1021 <a class="indexterm" name="id2558820"></a>
1022 To view the domain account access policies that may be configured execute:
1023 </p><pre class="screen">
1024 <code class="prompt">root# </code> pdbedit -P ?
1025 No account policy by that name
1026 Account policy names are :
1029 user must logon to change password
1030 maximum password age
1031 minimum password age
1036 refuse machine password change
1039 Commands will be executed to establish controls for our domain as follows:
1040 </p><div class="orderedlist"><ol type="1"><li><p>min password length = 8 characters.</p></li><li><p>password history = last 4 passwords.</p></li><li><p>maximum password age = 90 days.</p></li><li><p>minimum password age = 7 days.</p></li><li><p>bad lockout attempt = 8 bad logon attempts.</p></li><li><p>lockout duration = forever, account must be manually reenabled.</p></li></ol></div><p>
1041 The following command execution will achieve these settings:
1042 </p><pre class="screen">
1043 <code class="prompt">root# </code> pdbedit -P "min password length" -C 8
1044 account policy value for min password length was 5
1045 account policy value for min password length is now 8
1046 <code class="prompt">root# </code> pdbedit -P "password history" -C 4
1047 account policy value for password history was 0
1048 account policy value for password history is now 4
1049 <code class="prompt">root# </code> pdbedit -P "maximum password age" -C 90
1050 account policy value for maximum password age was 4294967295
1051 account policy value for maximum password age is now 90
1052 <code class="prompt">root# </code> pdbedit -P "minimum password age" -C 7
1053 account policy value for minimum password age was 0
1054 account policy value for minimum password age is now 7
1055 <code class="prompt">root# </code> pdbedit -P "bad lockout attempt" -C 8
1056 account policy value for bad lockout attempt was 0
1057 account policy value for bad lockout attempt is now 8
1058 <code class="prompt">root# </code> pdbedit -P "lockout duration" -C -1
1059 account policy value for lockout duration was 30
1060 account policy value for lockout duration is now 4294967295
1062 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
1063 To set the maximum (infinite) lockout time use the value of -1.
1064 </p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
1065 Account policies must be set individually on each PDC and BDC. At this time (Samba 3.0.11 to Samba 3.0.14a)
1066 account policies are not replicated automatically. This may be fixed before Samba 3.0.20 ships or some
1068 </p></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2558964"></a>Account Migration</h4></div></div></div><p>
1069 <a class="indexterm" name="id2558972"></a>
1070 <a class="indexterm" name="id2558978"></a>
1071 <a class="indexterm" name="id2558985"></a>
1072 The <span><strong class="command">pdbedit</strong></span> tool allows migration of authentication (account)
1073 databases from one backend to another. For example, to migrate accounts from an
1074 old <code class="filename">smbpasswd</code> database to a <em class="parameter"><code>tdbsam</code></em>
1076 </p><div class="procedure"><ol type="1"><li><p>
1077 Set the <a class="indexterm" name="id2559022"></a>passdb backend = tdbsam, smbpasswd.
1079 <a class="indexterm" name="id2559036"></a>
1081 </p><pre class="screen">
1082 <code class="prompt">root# </code><strong class="userinput"><code>pdbedit -i smbpasswd -e tdbsam</code></strong>
1085 <a class="indexterm" name="id2559066"></a>
1086 Remove the <em class="parameter"><code>smbpasswd</code></em> from the passdb backend
1087 configuration in <code class="filename">smb.conf</code>.
1088 </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="id2559092"></a>Password Backends</h2></div></div></div><p>
1089 <a class="indexterm" name="id2559100"></a>
1090 <a class="indexterm" name="id2559106"></a>
1091 Samba offers the greatest flexibility in backend account database design of any SMB/CIFS server
1092 technology available today. The flexibility is immediately obvious as one begins to explore this
1095 <a class="indexterm" name="id2559120"></a>
1096 <a class="indexterm" name="id2559127"></a>
1097 It is possible to specify not only multiple password backends, but even multiple
1098 backends of the same type. For example, to use two different <code class="literal">tdbsam</code> databases:
1100 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2559148"></a><em class="parameter"><code>passdb backend = tdbsam:/etc/samba/passdb.tdb tdbsam:/etc/samba/old-passdb.tdb</code></em></td></tr></table><p>
1102 What is possible is not always sensible. Be careful to avoid complexity to the point that it
1103 may be said that the solution is “<span class="quote">too clever by half!</span>”
1104 </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559169"></a>Plaintext</h3></div></div></div><p>
1105 <a class="indexterm" name="id2559177"></a>
1106 <a class="indexterm" name="id2559184"></a>
1107 <a class="indexterm" name="id2559191"></a>
1108 <a class="indexterm" name="id2559198"></a>
1109 <a class="indexterm" name="id2559205"></a>
1110 <a class="indexterm" name="id2559211"></a>
1111 Older versions of Samba retrieved user information from the UNIX user database
1112 and eventually some other fields from the file <code class="filename">/etc/samba/smbpasswd</code>
1113 or <code class="filename">/etc/smbpasswd</code>. When password encryption is disabled, no
1114 SMB-specific data is stored at all. Instead, all operations are conducted via the way
1115 that the Samba host OS will access its <code class="filename">/etc/passwd</code> database.
1116 On most Linux systems, for example, all user and group resolution is done via PAM.
1117 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559245"></a>smbpasswd: Encrypted Password Database</h3></div></div></div><p>
1118 <a class="indexterm" name="id2559253"></a>
1119 <a class="indexterm" name="id2559263"></a>
1120 <a class="indexterm" name="id2559270"></a>
1121 <a class="indexterm" name="id2559277"></a>
1122 Traditionally, when configuring <a class="indexterm" name="id2559284"></a>encrypt passwords = yes
1123 in Samba's <code class="filename">smb.conf</code> file, user account information such as username, LM/NT password hashes,
1124 password change times, and account flags have been stored in the <code class="filename">smbpasswd(5)</code>
1125 file. There are several disadvantages to this approach for sites with large numbers of users
1126 (counted in the thousands).
1127 </p><div class="itemizedlist"><ul type="disc"><li><p>
1128 <a class="indexterm" name="id2559315"></a>
1129 The first problem is that all lookups must be performed sequentially. Given that
1130 there are approximately two lookups per domain logon (one during intial logon validation
1131 and one for a session connection setup, such as when mapping a network drive or printer), this
1132 is a performance bottleneck for large sites. What is needed is an indexed approach
1133 such as that used in databases.
1135 <a class="indexterm" name="id2559332"></a>
1136 <a class="indexterm" name="id2559339"></a>
1137 <a class="indexterm" name="id2559346"></a>
1138 <a class="indexterm" name="id2559353"></a>
1139 <a class="indexterm" name="id2559359"></a>
1140 The second problem is that administrators who desire to replicate an smbpasswd file
1141 to more than one Samba server are left to use external tools such as
1142 <span><strong class="command">rsync(1)</strong></span> and <span><strong class="command">ssh(1)</strong></span> and write custom,
1145 <a class="indexterm" name="id2559386"></a>
1146 <a class="indexterm" name="id2559393"></a>
1147 <a class="indexterm" name="id2559400"></a>
1148 <a class="indexterm" name="id2559406"></a>
1149 <a class="indexterm" name="id2559413"></a>
1150 Finally, the amount of information that is stored in an smbpasswd entry leaves
1151 no room for additional attributes such as a home directory, password expiration time,
1152 or even a relative identifier (RID).
1153 </p></li></ul></div><p>
1154 <a class="indexterm" name="id2559430"></a>
1155 <a class="indexterm" name="id2559437"></a>
1156 <a class="indexterm" name="id2559444"></a>
1157 <a class="indexterm" name="id2559451"></a>
1158 As a result of these deficiencies, a more robust means of storing user attributes
1159 used by smbd was developed. The API that defines access to user accounts
1160 is commonly referred to as the samdb interface (previously, this was called the passdb
1161 API and is still so named in the Samba source code trees).
1163 <a class="indexterm" name="id2559466"></a>
1164 <a class="indexterm" name="id2559473"></a>
1165 <a class="indexterm" name="id2559480"></a>
1166 <a class="indexterm" name="id2559487"></a>
1167 <a class="indexterm" name="id2559494"></a>
1168 <a class="indexterm" name="id2559501"></a>
1169 Samba provides an enhanced set of passdb backends that overcome the deficiencies
1170 of the smbpasswd plaintext database. These are tdbsam, ldapsam, and xmlsam.
1171 Of these, ldapsam will be of most interest to large corporate or enterprise sites.
1172 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559514"></a>tdbsam</h3></div></div></div><p>
1173 <a class="indexterm" name="id2559522"></a>
1174 <a class="indexterm" name="id2559531"></a>
1175 <a class="indexterm" name="id2559540"></a>
1176 Samba can store user and machine account data in a “<span class="quote">TDB</span>” (trivial database).
1177 Using this backend does not require any additional configuration. This backend is
1178 recommended for new installations that do not require LDAP.
1180 <a class="indexterm" name="id2559557"></a>
1181 <a class="indexterm" name="id2559564"></a>
1182 <a class="indexterm" name="id2559570"></a>
1183 <a class="indexterm" name="id2559577"></a>
1184 As a general guide, the Samba Team does not recommend using the tdbsam backend for sites
1185 that have 250 or more users. Additionally, tdbsam is not capable of scaling for use
1186 in sites that require PDB/BDC implementations that require replication of the account
1187 database. Clearly, for reason of scalability, the use of ldapsam should be encouraged.
1189 <a class="indexterm" name="id2559593"></a>
1190 <a class="indexterm" name="id2559600"></a>
1191 <a class="indexterm" name="id2559607"></a>
1192 The recommendation of a 250-user limit is purely based on the notion that this
1193 would generally involve a site that has routed networks, possibly spread across
1194 more than one physical location. The Samba Team has not at this time established
1195 the performance-based scalability limits of the tdbsam architecture.
1197 <a class="indexterm" name="id2559622"></a>
1198 <a class="indexterm" name="id2559629"></a>
1199 <a class="indexterm" name="id2559636"></a>
1200 <a class="indexterm" name="id2559643"></a>
1201 There are sites that have thousands of users and yet require only one server.
1202 One site recently reported having 4,500 user accounts on one UNIX system and
1203 reported excellent performance with the <code class="literal">tdbsam</code> passdb backend.
1204 The limitation of where the <code class="literal">tdbsam</code> passdb backend can be used
1205 is not one pertaining to a limitation in the TDB storage system, it is based
1206 only on the need for a reliable distribution mechanism for the SambaSAMAccount
1208 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2559672"></a>ldapsam</h3></div></div></div><p>
1209 <a class="indexterm" name="id2559679"></a>
1210 <a class="indexterm" name="id2559686"></a>
1211 <a class="indexterm" name="id2559693"></a>
1212 There are a few points to stress that the ldapsam does not provide. The LDAP
1213 support referred to in this documentation does not include:
1214 </p><div class="itemizedlist"><ul type="disc"><li><p>A means of retrieving user account information from
1215 a Windows 200x Active Directory server.</p></li><li><p>A means of replacing /etc/passwd.</p></li></ul></div><p>
1216 <a class="indexterm" name="id2559722"></a>
1217 <a class="indexterm" name="id2559729"></a>
1218 <a class="indexterm" name="id2559735"></a>
1219 <a class="indexterm" name="id2559742"></a>
1220 The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be
1221 obtained from <a href="http://www.padl.com/" target="_top">PADL Software</a>. More information about the
1222 configuration of these packages may be found in <a href="http://safari.oreilly.com/?XmlId=1-56592-491-6" target="_top">
1223 <span class="emphasis"><em>LDAP, System Administration</em></span> by Gerald Carter, Chapter 6, Replacing NIS"</a>.
1225 <a class="indexterm" name="id2559773"></a>
1226 <a class="indexterm" name="id2559780"></a>
1227 <a class="indexterm" name="id2559786"></a>
1228 This document describes how to use an LDAP directory for storing Samba user
1229 account information traditionally stored in the smbpasswd(5) file. It is
1230 assumed that the reader already has a basic understanding of LDAP concepts
1231 and has a working directory server already installed. For more information
1232 on LDAP architectures and directories, please refer to the following sites:
1233 </p><div class="itemizedlist"><ul type="disc"><li><p><a href="http://www.openldap.org/" target="_top">OpenLDAP</a></p></li><li><p><a href="http://www.sun.com/software/products/directory_srvr_ee/index.xml" target="_top">
1234 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><a href="http://www-306.ibm.com/software/tivoli/products/directory-server/" target="_top">IBM
1235 Tivoli Directory Server</a></p></li><li><p><a href="http://www.redhat.com/software/rha/directory/" target="_top">Red Hat Directory
1236 Server</a></p></li><li><p><a href="http://www.linuxsecurity.com/content/view/119229" target="_top">Fedora Directory
1237 Server</a></p></li></ul></div><p>
1238 Two additional Samba resources that may prove to be helpful are:
1239 </p><div class="itemizedlist"><ul type="disc"><li><p>
1240 <a class="indexterm" name="id2559867"></a>
1241 The <a href="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" target="_top">Samba-PDC-LDAP-HOWTO</a>
1242 maintained by Ignacio Coupeau.
1244 <a class="indexterm" name="id2559886"></a>
1245 <a class="indexterm" name="id2559893"></a>
1246 <a class="indexterm" name="id2559900"></a>
1247 The NT migration scripts from <a href="http://samba.idealx.org/" target="_top">IDEALX</a> that are
1248 geared to manage users and groups in such a Samba-LDAP domain controller configuration.
1249 Idealx also produced the smbldap-tools and the Interactive Console Management tool.
1250 </p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2559919"></a>Supported LDAP Servers</h4></div></div></div><p>
1251 <a class="indexterm" name="id2559927"></a>
1252 <a class="indexterm" name="id2559934"></a>
1253 <a class="indexterm" name="id2559941"></a>
1254 <a class="indexterm" name="id2559948"></a>
1255 The LDAP ldapsam code was developed and tested using the OpenLDAP 2.x server and
1256 client libraries. The same code should work with Netscape's Directory Server and client SDK.
1257 However, there are bound to be compile errors and bugs. These should not be hard to fix.
1258 Please submit fixes via the process outlined in <a href="bugreport.html" title="Chapter 39. Reporting Bugs">Reporting Bugs</a>.
1260 Samba is capable of working with any standards-compliant LDAP server.
1261 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2559974"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div></div><p>
1262 Samba-3.0 includes the necessary schema file for OpenLDAP 2.x in the
1263 <code class="filename">examples/LDAP/samba.schema</code> directory of the source code distribution
1264 tarball. The schema entry for the sambaSamAccount ObjectClass is shown here:
1265 </p><pre class="programlisting">
1266 ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
1267 DESC 'Samba-3.0 Auxiliary SAM Account'
1268 MUST ( uid $ sambaSID )
1269 MAY ( cn $ sambaLMPassword $ sambaNTPassword $ sambaPwdLastSet $
1270 sambaLogonTime $ sambaLogoffTime $ sambaKickoffTime $
1271 sambaPwdCanChange $ sambaPwdMustChange $ sambaAcctFlags $
1272 displayName $ sambaHomePath $ sambaHomeDrive $ sambaLogonScript $
1273 sambaProfilePath $ description $ sambaUserWorkstations $
1274 sambaPrimaryGroupSID $ sambaDomainName ))
1277 <a class="indexterm" name="id2560010"></a>
1278 <a class="indexterm" name="id2560017"></a>
1279 <a class="indexterm" name="id2560024"></a>
1280 The <code class="filename">samba.schema</code> file has been formatted for OpenLDAP 2.0/2.1.
1281 The Samba Team owns the OID space used by the above schema and recommends its use.
1282 If you translate the schema to be used with Netscape DS, please submit the modified
1283 schema file as a patch to <a href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>.
1285 <a class="indexterm" name="id2560050"></a>
1286 <a class="indexterm" name="id2560057"></a>
1287 <a class="indexterm" name="id2560064"></a>
1288 <a class="indexterm" name="id2560071"></a>
1289 <a class="indexterm" name="id2560078"></a>
1290 <a class="indexterm" name="id2560085"></a>
1291 <a class="indexterm" name="id2560091"></a>
1292 Just as the smbpasswd file is meant to store information that provides information
1293 additional to a user's <code class="filename">/etc/passwd</code> entry, so is the sambaSamAccount
1294 object meant to supplement the UNIX user account information. A sambaSamAccount is an
1295 <code class="constant">AUXILIARY</code> ObjectClass, so it can be used to augment existing
1296 user account information in the LDAP directory, thus providing information needed
1297 for Samba account handling. However, there are several fields (e.g., uid) that overlap
1298 with the posixAccount ObjectClass outlined in RFC 2307. This is by design.
1300 <a class="indexterm" name="id2560120"></a>
1301 <a class="indexterm" name="id2560127"></a>
1302 <a class="indexterm" name="id2560134"></a>
1303 <a class="indexterm" name="id2560141"></a>
1304 <a class="indexterm" name="id2560148"></a>
1305 <a class="indexterm" name="id2560155"></a>
1306 <a class="indexterm" name="id2560162"></a>
1307 <a class="indexterm" name="id2560168"></a>
1308 <a class="indexterm" name="id2560175"></a>
1309 In order to store all user account information (UNIX and Samba) in the directory,
1310 it is necessary to use the sambaSamAccount and posixAccount ObjectClasses in
1311 combination. However, <span><strong class="command">smbd</strong></span> will still obtain the user's UNIX account
1312 information via the standard C library calls, such as getpwnam().
1313 This means that the Samba server must also have the LDAP NSS library installed
1314 and functioning correctly. This division of information makes it possible to
1315 store all Samba account information in LDAP, but still maintain UNIX account
1316 information in NIS while the network is transitioning to a full LDAP infrastructure.
1317 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2560200"></a>OpenLDAP Configuration</h4></div></div></div><p>
1318 <a class="indexterm" name="id2560208"></a>
1319 <a class="indexterm" name="id2560215"></a>
1320 <a class="indexterm" name="id2560222"></a>
1321 <a class="indexterm" name="id2560229"></a>
1322 To include support for the sambaSamAccount object in an OpenLDAP directory
1323 server, first copy the samba.schema file to slapd's configuration directory.
1324 The samba.schema file can be found in the directory <code class="filename">examples/LDAP</code>
1325 in the Samba source distribution.
1326 </p><pre class="screen">
1327 <code class="prompt">root# </code><strong class="userinput"><code>cp samba.schema /etc/openldap/schema/</code></strong>
1330 <a class="indexterm" name="id2560266"></a>
1331 <a class="indexterm" name="id2560273"></a>
1332 <a class="indexterm" name="id2560279"></a>
1333 <a class="indexterm" name="id2560286"></a>
1334 <a class="indexterm" name="id2560293"></a>
1335 <a class="indexterm" name="id2560300"></a>
1336 <a class="indexterm" name="id2560307"></a>
1337 <a class="indexterm" name="id2560314"></a>
1338 Next, include the <code class="filename">samba.schema</code> file in <code class="filename">slapd.conf</code>.
1339 The sambaSamAccount object contains two attributes that depend on other schema
1340 files. The <em class="parameter"><code>uid</code></em> attribute is defined in <code class="filename">cosine.schema</code> and
1341 the <em class="parameter"><code>displayName</code></em> attribute is defined in the <code class="filename">inetorgperson.schema</code>
1342 file. Both of these must be included before the <code class="filename">samba.schema</code> file.
1343 </p><pre class="programlisting">
1344 ## /etc/openldap/slapd.conf
1346 ## schema files (core.schema is required by default)
1347 include /etc/openldap/schema/core.schema
1349 ## needed for sambaSamAccount
1350 include /etc/openldap/schema/cosine.schema
1351 include /etc/openldap/schema/inetorgperson.schema
1352 include /etc/openldap/schema/nis.schema
1353 include /etc/openldap/schema/samba.schema
1357 <a class="indexterm" name="id2560382"></a>
1358 <a class="indexterm" name="id2560389"></a>
1359 <a class="indexterm" name="id2560396"></a>
1360 <a class="indexterm" name="id2560402"></a>
1361 It is recommended that you maintain some indices on some of the most useful attributes,
1362 as in the following example, to speed up searches made on sambaSamAccount ObjectClasses
1363 (and possibly posixAccount and posixGroup as well):
1365 </p><pre class="programlisting">
1366 # Indices to maintain
1367 ## required by OpenLDAP
1368 index objectclass eq
1370 index cn pres,sub,eq
1371 index sn pres,sub,eq
1372 ## required to support pdb_getsampwnam
1373 index uid pres,sub,eq
1374 ## required to support pdb_getsambapwrid()
1375 index displayName pres,sub,eq
1377 ## uncomment these if you are storing posixAccount and
1378 ## posixGroup entries in the directory as well
1379 ##index uidNumber eq
1380 ##index gidNumber eq
1381 ##index memberUid eq
1384 index sambaPrimaryGroupSID eq
1385 index sambaDomainName eq
1389 Create the new index by executing:
1390 </p><pre class="screen">
1391 <code class="prompt">root# </code>./sbin/slapindex -f slapd.conf
1394 Remember to restart slapd after making these changes:
1395 </p><pre class="screen">
1396 <code class="prompt">root# </code><strong class="userinput"><code>/etc/init.d/slapd restart</code></strong>
1398 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2560472"></a>Initialize the LDAP Database</h4></div></div></div><p>
1399 <a class="indexterm" name="id2560480"></a>
1400 <a class="indexterm" name="id2560487"></a>
1401 <a class="indexterm" name="id2560494"></a>
1402 <a class="indexterm" name="id2560501"></a>
1403 Before you can add accounts to the LDAP database, you must create the account containers
1404 that they will be stored in. The following LDIF file should be modified to match your
1405 needs (DNS entries, and so on):
1406 </p><pre class="programlisting">
1407 # Organization for Samba Base
1408 dn: dc=quenya,dc=org
1409 objectclass: dcObject
1410 objectclass: organization
1412 o: Quenya Org Network
1413 description: The Samba-3 Network LDAP Example
1415 # Organizational Role for Directory Management
1416 dn: cn=Manager,dc=quenya,dc=org
1417 objectclass: organizationalRole
1419 description: Directory Manager
1421 # Setting up container for Users OU
1422 dn: ou=People,dc=quenya,dc=org
1424 objectclass: organizationalUnit
1427 # Setting up admin handle for People OU
1428 dn: cn=admin,ou=People,dc=quenya,dc=org
1431 objectclass: organizationalRole
1432 objectclass: simpleSecurityObject
1433 userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
1435 # Setting up container for groups
1436 dn: ou=Groups,dc=quenya,dc=org
1438 objectclass: organizationalUnit
1441 # Setting up admin handle for Groups OU
1442 dn: cn=admin,ou=Groups,dc=quenya,dc=org
1445 objectclass: organizationalRole
1446 objectclass: simpleSecurityObject
1447 userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
1449 # Setting up container for computers
1450 dn: ou=Computers,dc=quenya,dc=org
1452 objectclass: organizationalUnit
1455 # Setting up admin handle for Computers OU
1456 dn: cn=admin,ou=Computers,dc=quenya,dc=org
1459 objectclass: organizationalRole
1460 objectclass: simpleSecurityObject
1461 userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
1464 <a class="indexterm" name="id2560544"></a>
1465 <a class="indexterm" name="id2560551"></a>
1466 The userPassword shown above should be generated using <span><strong class="command">slappasswd</strong></span>.
1468 <a class="indexterm" name="id2560568"></a>
1469 <a class="indexterm" name="id2560574"></a>
1470 The following command will then load the contents of the LDIF file into the LDAP
1472 <a class="indexterm" name="id2560583"></a>
1473 </p><pre class="screen">
1474 <code class="prompt">$ </code><strong class="userinput"><code>slapadd -v -l initldap.dif</code></strong>
1477 Do not forget to secure your LDAP server with an adequate access control list
1478 as well as an admin password.
1479 </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
1480 <a class="indexterm" name="id2560615"></a>
1481 Before Samba can access the LDAP server, you need to store the LDAP admin password
1482 in the Samba-3 <code class="filename">secrets.tdb</code> database by:
1483 <a class="indexterm" name="id2560630"></a>
1484 </p><pre class="screen">
1485 <code class="prompt">root# </code><strong class="userinput"><code>smbpasswd -w <em class="replaceable"><code>secret</code></em></code></strong>
1487 </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2560658"></a>Configuring Samba</h4></div></div></div><p>
1488 <a class="indexterm" name="id2560665"></a>
1489 <a class="indexterm" name="id2560672"></a>
1490 The following parameters are available in <code class="filename">smb.conf</code> only if your version of Samba was built with
1491 LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found. The
1492 best method to verify that Samba was built with LDAP support is:
1493 </p><pre class="screen">
1494 <code class="prompt">root# </code> smbd -b | grep LDAP
1497 HAVE_LDAP_DOMAIN2HOSTLIST
1499 HAVE_LDAP_INITIALIZE
1500 HAVE_LDAP_SET_REBIND_PROC
1502 LDAP_SET_REBIND_PROC_ARGS
1504 If the build of the <span><strong class="command">smbd</strong></span> command you are using does not produce output
1505 that includes <code class="literal">HAVE_LDAP_H</code> it is necessary to discover why the LDAP headers
1506 and libraries were not found during compilation.
1507 </p><p>LDAP-related smb.conf options include these:
1508 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2560729"></a><em class="parameter"><code>passdb backend = ldapsam:url</code></em></td></tr><tr><td><a class="indexterm" name="id2560742"></a><em class="parameter"><code>ldap admin dn</code></em></td></tr><tr><td><a class="indexterm" name="id2560755"></a><em class="parameter"><code>ldap delete dn</code></em></td></tr><tr><td><a class="indexterm" name="id2560767"></a><em class="parameter"><code>ldap filter</code></em></td></tr><tr><td><a class="indexterm" name="id2560780"></a><em class="parameter"><code>ldap group suffix</code></em></td></tr><tr><td><a class="indexterm" name="id2560793"></a><em class="parameter"><code>ldap idmap suffix</code></em></td></tr><tr><td><a class="indexterm" name="id2560806"></a><em class="parameter"><code>ldap machine suffix</code></em></td></tr><tr><td><a class="indexterm" name="id2560818"></a><em class="parameter"><code>ldap passwd sync</code></em></td></tr><tr><td><a class="indexterm" name="id2560831"></a><em class="parameter"><code>ldap ssl</code></em></td></tr><tr><td><a class="indexterm" name="id2560844"></a><em class="parameter"><code>ldap suffix</code></em></td></tr><tr><td><a class="indexterm" name="id2560856"></a><em class="parameter"><code>ldap user suffix</code></em></td></tr><tr><td><a class="indexterm" name="id2560869"></a><em class="parameter"><code>ldap replication sleep</code></em></td></tr><tr><td><a class="indexterm" name="id2560882"></a><em class="parameter"><code>ldap timeout</code></em></td></tr><tr><td><a class="indexterm" name="id2560895"></a><em class="parameter"><code>ldap page size</code></em></td></tr></table><p>
1510 These are described in the <code class="filename">smb.conf</code> man page and so are not repeated here. However, an example
1511 for use with an LDAP directory is shown in <a href="passdb.html#confldapex" title="Example 10.2. Configuration with LDAP">the Configuration with LDAP.</a>
1512 </p><div class="example"><a name="confldapex"></a><p class="title"><b>Example 10.2. Configuration with LDAP</b></p><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="id2560952"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id2560965"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2560978"></a><em class="parameter"><code>netbios name = MORIA</code></em></td></tr><tr><td><a class="indexterm" name="id2560991"></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="id2561028"></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="id2561050"></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="id2561067"></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="id2561084"></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="id2561105"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2561118"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2561131"></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="id2561157"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr></table></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2561172"></a>Accounts and Groups Management</h4></div></div></div><p>
1513 <a class="indexterm" name="id2561180"></a>
1514 <a class="indexterm" name="id2561187"></a>
1515 Because user accounts are managed through the sambaSamAccount ObjectClass, you should
1516 modify your existing administration tools to deal with sambaSamAccount attributes.
1518 <a class="indexterm" name="id2561203"></a>
1519 <a class="indexterm" name="id2561210"></a>
1520 <a class="indexterm" name="id2561217"></a>
1521 Machine accounts are managed with the sambaSamAccount ObjectClass, just
1522 like user accounts. However, it is up to you to store those accounts
1523 in a different tree of your LDAP namespace. You should use
1524 “<span class="quote">ou=Groups,dc=quenya,dc=org</span>” to store groups and
1525 “<span class="quote">ou=People,dc=quenya,dc=org</span>” to store users. Just configure your
1526 NSS and PAM accordingly (usually, in the <code class="filename">/etc/openldap/sldap.conf</code>
1527 configuration file).
1529 <a class="indexterm" name="id2561246"></a>
1530 <a class="indexterm" name="id2561253"></a>
1531 <a class="indexterm" name="id2561260"></a>
1532 <a class="indexterm" name="id2561267"></a>
1533 In Samba-3, the group management system is based on POSIX
1534 groups. This means that Samba makes use of the posixGroup ObjectClass.
1535 For now, there is no NT-like group system management (global and local
1536 groups). Samba-3 knows only about <code class="constant">Domain Groups</code>
1537 and, unlike MS Windows 2000 and Active Directory, Samba-3 does not
1538 support nested groups.
1539 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2561285"></a>Security and sambaSamAccount</h4></div></div></div><p>
1540 <a class="indexterm" name="id2561293"></a>
1541 There are two important points to remember when discussing the security
1542 of sambaSAMAccount entries in the directory.
1543 </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Never</em></span> retrieve the SambaLMPassword or
1544 <a class="indexterm" name="id2561312"></a>
1545 SambaNTPassword attribute values over an unencrypted LDAP session.</p></li><li><p><span class="emphasis"><em>Never</em></span> allow non-admin users to
1546 view the SambaLMPassword or SambaNTPassword attribute values.</p></li></ul></div><p>
1547 <a class="indexterm" name="id2561333"></a>
1548 <a class="indexterm" name="id2561340"></a>
1549 <a class="indexterm" name="id2561346"></a>
1550 These password hashes are clear-text equivalents and can be used to impersonate
1551 the user without deriving the original clear-text strings. For more information
1552 on the details of LM/NT password hashes, refer to <a href="passdb.html" title="Chapter 10. Account Information Databases">the
1553 Account Information Database section</a>.
1555 <a class="indexterm" name="id2561368"></a>
1556 <a class="indexterm" name="id2561375"></a>
1557 <a class="indexterm" name="id2561382"></a>
1558 <a class="indexterm" name="id2561388"></a>
1559 To remedy the first security issue, the <a class="indexterm" name="id2561396"></a>ldap ssl <code class="filename">smb.conf</code>
1560 parameter defaults to require an encrypted session (<a class="indexterm" name="id2561410"></a>ldap ssl = on) using the default port of <code class="constant">636</code> when
1561 contacting the directory server. When using an OpenLDAP server, it
1562 is possible to use the StartTLS LDAP extended operation in the place of LDAPS.
1563 In either case, you are strongly encouraged to use secure communications protocols
1564 (so do not set <a class="indexterm" name="id2561426"></a>ldap ssl = off).
1566 <a class="indexterm" name="id2561436"></a>
1567 <a class="indexterm" name="id2561443"></a>
1568 <a class="indexterm" name="id2561450"></a>
1569 Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS
1570 extended operation. However, the OpenLDAP library still provides support for
1571 the older method of securing communication between clients and servers.
1573 <a class="indexterm" name="id2561464"></a>
1574 <a class="indexterm" name="id2561471"></a>
1575 <a class="indexterm" name="id2561478"></a>
1576 The second security precaution is to prevent non-administrative users from
1577 harvesting password hashes from the directory. This can be done using the
1578 following ACL in <code class="filename">slapd.conf</code>:
1580 </p><pre class="programlisting">
1581 ## allow the "ldap admin dn" access, but deny everyone else
1582 access to attrs=SambaLMPassword,SambaNTPassword
1583 by dn="cn=Samba Admin,ou=People,dc=quenya,dc=org" write
1586 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2561508"></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 10.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A">Part A</a>, and <a href="passdb.html#attribobjclPartB" title="Table 10.4. Attributes in the sambaSamAccount ObjectClass (LDAP), Part B">Part B</a>.
1587 </p><div class="table"><a name="attribobjclPartA"></a><p class="title"><b>Table 10.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A</b></p><table summary="Attributes in the sambaSamAccount ObjectClass (LDAP), Part A" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="justify"><code class="constant">sambaLMPassword</code></td><td align="justify">The LanMan password 16-byte hash stored as a character
1588 representation of a hexadecimal string.</td></tr><tr><td align="justify"><code class="constant">sambaNTPassword</code></td><td align="justify">The NT password 16-byte hash stored as a character
1589 representation of a hexadecimal string.</td></tr><tr><td align="justify"><code class="constant">sambaPwdLastSet</code></td><td align="justify">The integer time in seconds since 1970 when the
1590 <code class="constant">sambaLMPassword</code> and <code class="constant">sambaNTPassword</code> attributes were last set.
1591 </td></tr><tr><td align="justify"><code class="constant">sambaAcctFlags</code></td><td align="justify">String of 11 characters surrounded by square brackets [ ]
1592 representing account flags such as U (user), W (workstation), X (no password expiration),
1593 I (domain trust account), H (home dir required), S (server trust account),
1594 and D (disabled).</td></tr><tr><td align="justify"><code class="constant">sambaLogonTime</code></td><td align="justify">Integer value currently unused.</td></tr><tr><td align="justify"><code class="constant">sambaLogoffTime</code></td><td align="justify">Integer value currently unused.</td></tr><tr><td align="justify"><code class="constant">sambaKickoffTime</code></td><td align="justify">Specifies the time (UNIX time format) when the user
1595 will be locked down and cannot login any longer. If this attribute is omitted, then the account will never expire.
1596 Using this attribute together with shadowExpire of the shadowAccount ObjectClass will enable accounts to
1597 expire completely on an exact date.</td></tr><tr><td align="justify"><code class="constant">sambaPwdCanChange</code></td><td align="justify">Specifies the time (UNIX time format)
1598 after which the user is allowed to change his password. If this attribute is not set, the user will be free
1599 to change his password whenever he wants.</td></tr><tr><td align="justify"><code class="constant">sambaPwdMustChange</code></td><td align="justify">Specifies the time (UNIX time format) when the user is
1600 forced to change his password. If this value is set to 0, the user will have to change his password at first login.
1601 If this attribute is not set, then the password will never expire.</td></tr><tr><td align="justify"><code class="constant">sambaHomeDrive</code></td><td align="justify">Specifies the drive letter to which to map the
1602 UNC path specified by sambaHomePath. The drive letter must be specified in the form “<span class="quote">X:</span>”
1603 where X is the letter of the drive to map. Refer to the “<span class="quote">logon drive</span>” parameter in the
1604 smb.conf(5) man page for more information.</td></tr><tr><td align="justify"><code class="constant">sambaLogonScript</code></td><td align="justify">The sambaLogonScript property specifies the path of
1605 the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path
1606 is relative to the netlogon share. Refer to the <a class="indexterm" name="id2561700"></a>logon script parameter in the
1607 <code class="filename">smb.conf</code> man page for more information.</td></tr><tr><td align="justify"><code class="constant">sambaProfilePath</code></td><td align="justify">Specifies a path to the user's profile.
1608 This value can be a null string, a local absolute path, or a UNC path. Refer to the
1609 <a class="indexterm" name="id2561724"></a>logon path parameter in the <code class="filename">smb.conf</code> man page for more information.</td></tr><tr><td align="justify"><code class="constant">sambaHomePath</code></td><td align="justify">The sambaHomePath property specifies the path of
1610 the home directory for the user. The string can be null. If sambaHomeDrive is set and specifies
1611 a drive letter, sambaHomePath should be a UNC path. The path must be a network
1612 UNC path of the form <code class="filename">\\server\share\directory</code>. This value can be a null string.
1613 Refer to the <span><strong class="command">logon home</strong></span> parameter in the <code class="filename">smb.conf</code> man page for more information.
1614 </td></tr></tbody></table></div><div class="table"><a name="attribobjclPartB"></a><p class="title"><b>Table 10.4. Attributes in the sambaSamAccount ObjectClass (LDAP), Part B</b></p><table summary="Attributes in the sambaSamAccount ObjectClass (LDAP), Part B" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="justify"><code class="constant">sambaUserWorkstations</code></td><td align="justify">Here you can give a comma-separated list of machines
1615 on which the user is allowed to login. You may observe problems when you try to connect to a Samba domain member.
1616 Because domain members are not in this list, the domain controllers will reject them. Where this attribute is omitted,
1617 the default implies no restrictions.
1618 </td></tr><tr><td align="justify"><code class="constant">sambaSID</code></td><td align="justify">The security identifier(SID) of the user.
1619 The Windows equivalent of UNIX UIDs.</td></tr><tr><td align="justify"><code class="constant">sambaPrimaryGroupSID</code></td><td align="justify">The security identifier (SID) of the primary group
1620 of the user.</td></tr><tr><td align="justify"><code class="constant">sambaDomainName</code></td><td align="justify">Domain the user is part of.</td></tr></tbody></table></div><p>
1621 <a class="indexterm" name="id2561849"></a>
1622 <a class="indexterm" name="id2561855"></a>
1623 The majority of these parameters are only used when Samba is acting as a PDC of
1624 a domain (refer to <a href="samba-pdc.html" title="Chapter 4. Domain Control">Domain Control</a>, for details on
1625 how to configure Samba as a PDC). The following four attributes
1626 are only stored with the sambaSamAccount entry if the values are non-default values:
1627 </p><div class="itemizedlist"><a class="indexterm" name="id2561878"></a><a class="indexterm" name="id2561884"></a><a class="indexterm" name="id2561891"></a><a class="indexterm" name="id2561898"></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>
1628 <a class="indexterm" name="id2561927"></a>
1629 <a class="indexterm" name="id2561934"></a>
1630 <a class="indexterm" name="id2561940"></a>
1631 These attributes are only stored with the sambaSamAccount entry if
1632 the values are non-default values. For example, assume MORIA has now been
1633 configured as a PDC and that <a class="indexterm" name="id2561950"></a>logon home = \\%L\%u was defined in
1634 its <code class="filename">smb.conf</code> file. When a user named “<span class="quote">becky</span>” logs on to the domain,
1635 the <a class="indexterm" name="id2561968"></a>logon home string is expanded to \\MORIA\becky.
1636 If the smbHome attribute exists in the entry “<span class="quote">uid=becky,ou=People,dc=samba,dc=org</span>”,
1637 this value is used. However, if this attribute does not exist, then the value
1638 of the <a class="indexterm" name="id2561982"></a>logon home parameter is used in its place. Samba
1639 will only write the attribute value to the directory entry if the value is
1640 something other than the default (e.g., <code class="filename">\\MOBY\becky</code>).
1641 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2562000"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div></div><p>
1642 The following is a working LDIF that demonstrates the use of the SambaSamAccount ObjectClass:
1643 </p><pre class="programlisting">
1644 dn: uid=guest2, ou=People,dc=quenya,dc=org
1645 sambaLMPassword: 878D8014606CDA29677A44EFA1353FC7
1646 sambaPwdMustChange: 2147483647
1647 sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-513
1648 sambaNTPassword: 552902031BEDE9EFAAD3B435B51404EE
1649 sambaPwdLastSet: 1010179124
1651 objectClass: sambaSamAccount
1653 sambaKickoffTime: 2147483647
1654 sambaAcctFlags: [UX ]
1655 sambaLogoffTime: 2147483647
1656 sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5006
1657 sambaPwdCanChange: 0
1660 The following is an LDIF entry for using both the sambaSamAccount and
1661 posixAccount ObjectClasses:
1662 </p><pre class="programlisting">
1663 dn: uid=gcarter, ou=People,dc=quenya,dc=org
1665 displayName: Gerald Carter
1666 sambaLMPassword: 552902031BEDE9EFAAD3B435B51404EE
1667 sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-1201
1668 objectClass: posixAccount
1669 objectClass: sambaSamAccount
1670 sambaAcctFlags: [UX ]
1671 userPassword: {crypt}BpM2ej8Rkzogo
1675 loginShell: /bin/bash
1676 logoffTime: 2147483647
1678 sambaKickoffTime: 2147483647
1679 sambaPwdLastSet: 1010179230
1680 sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5004
1681 homeDirectory: /home/moria/gcarter
1682 sambaPwdCanChange: 0
1683 sambaPwdMustChange: 2147483647
1684 sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7
1686 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2562049"></a>Password Synchronization</h4></div></div></div><p>
1687 Samba-3 and later can update the non-Samba (LDAP) password stored with an account. When
1688 using pam_ldap, this allows changing both UNIX and Windows passwords at once.
1689 </p><p>The <a class="indexterm" name="id2562063"></a>ldap passwd sync options can have the values shown in
1690 <a href="passdb.html#ldappwsync" title="Table 10.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 10.5. Possible <em class="parameter"><code>ldap passwd sync</code></em> Values</b></p><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
1691 <code class="constant">SambaNTPassword</code>, <code class="constant">SambaLMPassword</code>,
1692 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
1693 <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
1694 worry about the other fields. This option is only available on some LDAP servers and
1695 only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.</p></td></tr></tbody></table></div><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="id2562196"></a>Using OpenLDAP Overlay for Password Syncronization</h4></div></div></div><p>
1696 Howard Chu has written a special overlay called <span><strong class="command">smbk5pwd</strong></span>. This tool modifies the
1697 <code class="literal">SambaNTPassword</code>, <code class="literal">SambaLMPassword</code> and <code class="literal">Heimdal</code>
1698 hashes in an OpenLDAP entry when an LDAP_EXOP_X_MODIFY_PASSWD operation is performed.
1700 The overlay is shipped with OpenLDAP-2.3 and can be found in the
1701 <code class="filename">contrib/slapd-modules/smbk5pwd</code> subdirectory. This module can also be used with
1703 </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2562246"></a>MySQL</h3></div></div></div><p>
1704 <a class="indexterm" name="id2562254"></a>
1705 <a class="indexterm" name="id2562263"></a>
1706 Every so often someone comes along with what seems (to them) like a great new idea. Storing user accounts
1707 in an SQL backend is one of them. Those who want to do this are in the best position to know what the
1708 specific benefits are to them. This may sound like a cop-out, but in truth we cannot document
1709 every little detail of why certain things of marginal utility to the bulk of Samba users might make sense
1710 to the rest. In any case, the following instructions should help the determined SQL user to implement a
1711 working system. These account storage methods are not actively maintained by the Samba Team.
1712 </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2562281"></a>Creating the Database</h4></div></div></div><p>
1713 <a class="indexterm" name="id2562289"></a>
1714 You can set up your own table and specify the field names to pdb_mysql (see
1715 <a href="passdb.html#moremysqlpdbe" title="Table 10.7. MySQL field names for MySQL passdb backend">MySQL field names for MySQL passdb backend</a> for
1716 the column names) or use the default table. The file
1717 <code class="filename">examples/pdb/mysql/mysql.dump</code> contains the correct queries to
1718 create the required tables. Use the command:
1719 </p><pre class="screen">
1720 <code class="prompt">root# </code><strong class="userinput"><code>mysql -u<em class="replaceable"><code>username</code></em> -h<em class="replaceable"><code>hostname</code></em> -p<em class="replaceable"><code>password</code></em> \
1721 <em class="replaceable"><code>databasename</code></em> < <code class="filename">/path/to/samba/examples/pdb/mysql/mysql.dump</code></code></strong>
1723 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2562353"></a>Configuring</h4></div></div></div><p>This plug-in lacks some good documentation, but here is some brief information. Add the following to the
1724 <a class="indexterm" name="id2562363"></a>passdb backend variable in your <code class="filename">smb.conf</code>:
1725 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2562382"></a><em class="parameter"><code>passdb backend = [other-plugins] mysql:identifier [other-plugins]</code></em></td></tr></table><p>
1726 </p><p>The identifier can be any string you like, as long as it does not collide with
1727 the identifiers of other plugins or other instances of pdb_mysql. If you
1728 specify multiple pdb_mysql.so entries in <a class="indexterm" name="id2562402"></a>passdb backend, you also need to
1729 use different identifiers.
1731 Additional options can be given through the <code class="filename">smb.conf</code> file in the <em class="parameter"><code>[global]</code></em> section.
1732 Refer to <a href="passdb.html#mysqlpbe" title="Table 10.6. Basic smb.conf Options for MySQL passdb Backend">Basic smb.conf Options for MySQL passdb Backend</a>.
1733 </p><div class="table"><a name="mysqlpbe"></a><p class="title"><b>Table 10.6. Basic smb.conf Options for MySQL passdb Backend</b></p><table summary="Basic smb.conf Options for MySQL passdb Backend" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Field</th><th align="justify">Contents</th></tr></thead><tbody><tr><td align="left">mysql host</td><td align="justify">Host name, defaults to `localhost'</td></tr><tr><td align="left">mysql password</td><td align="justify"> </td></tr><tr><td align="left">mysql user</td><td align="justify">Defaults to `samba'</td></tr><tr><td align="left">mysql database</td><td align="justify">Defaults to `samba'</td></tr><tr><td align="left">mysql port</td><td align="justify">Defaults to 3306</td></tr><tr><td align="left">table</td><td align="justify">Name of the table containing the users</td></tr></tbody></table></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
1734 Since the password for the MySQL user is stored in the <code class="filename">smb.conf</code> file, you should make the <code class="filename">smb.conf</code> file
1735 readable only to the user who runs Samba. This is considered a security bug and will soon be fixed.
1736 </p></div><p>Names of the columns are given in <a href="passdb.html#moremysqlpdbe" title="Table 10.7. MySQL field names for MySQL passdb backend">MySQL field names for MySQL
1737 passdb backend</a>. The default column names can be found in the example table dump.
1739 </p><div class="table"><a name="moremysqlpdbe"></a><p class="title"><b>Table 10.7. MySQL field names for MySQL passdb backend</b></p><table summary="MySQL field names for MySQL passdb backend" border="1"><colgroup><col align="left"><col align="left"><col align="justify"></colgroup><thead><tr><th align="justify">Field</th><th align="justify">Type</th><th align="justify">Contents</th></tr></thead><tbody><tr><td align="justify">logon time column</td><td align="justify">int(9)</td><td align="justify">UNIX timestamp of last logon of user</td></tr><tr><td align="justify">logoff time column</td><td align="justify">int(9)</td><td align="justify">UNIX timestamp of last logoff of user</td></tr><tr><td align="justify">kickoff time column</td><td align="justify">int(9)</td><td align="justify">UNIX timestamp of moment user should be kicked off workstation (not enforced)</td></tr><tr><td align="justify">pass last set time column</td><td align="justify">int(9)</td><td align="justify">UNIX timestamp of moment password was last set</td></tr><tr><td align="justify">pass can change time column</td><td align="justify">int(9)</td><td align="justify">UNIX timestamp of moment from which password can be changed</td></tr><tr><td align="justify">pass must change time column</td><td align="justify">int(9)</td><td align="justify">UNIX timestamp of moment on which password must be changed</td></tr><tr><td align="justify">username column</td><td align="justify">varchar(255)</td><td align="justify">UNIX username</td></tr><tr><td align="justify">domain column</td><td align="justify">varchar(255)</td><td align="justify">NT domain user belongs to</td></tr><tr><td align="justify">nt username column</td><td align="justify">varchar(255)</td><td align="justify">NT username</td></tr><tr><td align="justify">fullname column</td><td align="justify">varchar(255)</td><td align="justify">Full name of user</td></tr><tr><td align="justify">home dir column</td><td align="justify">varchar(255)</td><td align="justify">UNIX homedir path (equivalent of the <a class="indexterm" name="id2562714"></a>logon home parameter.</td></tr><tr><td align="justify">dir drive column</td><td align="justify">varchar(2)</td><td align="justify">Directory drive path (e.g., “<span class="quote">H:</span>”)</td></tr><tr><td align="justify">logon script column</td><td align="justify">varchar(255)</td><td align="justify">Batch file to run on client side when logging on</td></tr><tr><td align="justify">profile path column</td><td align="justify">varchar(255)</td><td align="justify">Path of profile</td></tr><tr><td align="justify">acct desc column</td><td align="justify">varchar(255)</td><td align="justify">Some ASCII NT user data</td></tr><tr><td align="justify">workstations column</td><td align="justify">varchar(255)</td><td align="justify">Workstations user can logon to (or NULL for all)</td></tr><tr><td align="justify">unknown string column</td><td align="justify">varchar(255)</td><td align="justify">Unknown string</td></tr><tr><td align="justify">munged dial column</td><td align="justify">varchar(255)</td><td align="justify">Unknown</td></tr><tr><td align="justify">user sid column</td><td align="justify">varchar(255)</td><td align="justify">NT user SID</td></tr><tr><td align="justify">group sid column</td><td align="justify">varchar(255)</td><td align="justify">NT group SID</td></tr><tr><td align="justify">lanman pass column</td><td align="justify">varchar(255)</td><td align="justify">Encrypted lanman password</td></tr><tr><td align="justify">nt pass column</td><td align="justify">varchar(255)</td><td align="justify">Encrypted nt passwd</td></tr><tr><td align="justify">plain pass column</td><td align="justify">varchar(255)</td><td align="justify">Plaintext password</td></tr><tr><td align="justify">acct ctrl column</td><td align="justify">int(9)</td><td align="justify">NT user data</td></tr><tr><td align="justify">unknown 3 column</td><td align="justify">int(9)</td><td align="justify">Unknown</td></tr><tr><td align="justify">logon divs column</td><td align="justify">int(9)</td><td align="justify">Unknown</td></tr><tr><td align="justify">hours len column</td><td align="justify">int(9)</td><td align="justify">Unknown</td></tr><tr><td align="justify">bad password count column</td><td align="justify">int(5)</td><td align="justify">Number of failed password tries before disabling an account</td></tr><tr><td align="justify">logon count column</td><td align="justify">int(5)</td><td align="justify">Number of logon attempts</td></tr><tr><td align="justify">unknown 6 column</td><td align="justify">int(9)</td><td align="justify">Unknown</td></tr></tbody></table></div><p>
1741 You can put a colon (:) after the name of each column, which
1742 should specify the column to update when updating the table. You can also specify nothing behind the colon, in which case the field data will not be updated. Setting a column name to <em class="parameter"><code>NULL</code></em> means the field should not be used.
1743 </p><p><a href="passdb.html#mysqlsam" title="Example 10.3. Example Configuration for the MySQL passdb Backend">An example configuration</a> is shown in <a href="passdb.html#mysqlsam" title="Example 10.3. Example Configuration for the MySQL passdb Backend">Example Configuration for the MySQL passdb Backend</a>.
1744 </p><div class="example"><a name="mysqlsam"></a><p class="title"><b>Example 10.3. Example Configuration for the MySQL passdb Backend</b></p><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="id2562972"></a><em class="parameter"><code>passdb backend = mysql:foo</code></em></td></tr><tr><td><a class="indexterm" name="id2562985"></a><em class="parameter"><code>foo:mysql user = samba</code></em></td></tr><tr><td><a class="indexterm" name="id2562998"></a><em class="parameter"><code>foo:mysql password = abmas</code></em></td></tr><tr><td><a class="indexterm" name="id2563011"></a><em class="parameter"><code>foo:mysql database = samba</code></em></td></tr><tr><td># domain name is static and can't be changed</td></tr><tr><td><a class="indexterm" name="id2563028"></a><em class="parameter"><code>foo:domain column = 'MYWORKGROUP':</code></em></td></tr><tr><td># The fullname column comes from several other columns</td></tr><tr><td><a class="indexterm" name="id2563045"></a><em class="parameter"><code>foo:fullname column = CONCAT(firstname,' ',surname):</code></em></td></tr><tr><td># Samba should never write to the password columns</td></tr><tr><td><a class="indexterm" name="id2563063"></a><em class="parameter"><code>foo:lanman pass column = lm_pass:</code></em></td></tr><tr><td><a class="indexterm" name="id2563076"></a><em class="parameter"><code>foo:nt pass column = nt_pass:</code></em></td></tr><tr><td># The unknown 3 column is not stored</td></tr><tr><td><a class="indexterm" name="id2563093"></a><em class="parameter"><code>foo:unknown 3 column = NULL</code></em></td></tr></table></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2563108"></a>Using Plaintext Passwords or Encrypted Password</h4></div></div></div><p>
1745 <a class="indexterm" name="id2563117"></a>
1746 I strongly discourage the use of plaintext passwords; however, you can use them.
1748 <a class="indexterm" name="id2563128"></a>
1749 If you would like to use plaintext passwords, set
1750 `identifier:lanman pass column' and `identifier:nt pass column' to
1751 `NULL' (without the quotes) and `identifier:plain pass column' to the
1752 name of the column containing the plaintext passwords.
1754 If you use encrypted passwords, set the 'identifier:plain pass
1755 column' to 'NULL' (without the quotes). This is the default.
1756 </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2563147"></a>Getting Non-Column Data from the Table</h4></div></div></div><p>
1757 It is possible to have not all data in the database by making some "constant."
1759 For example, you can set `identifier:fullname column' to
1760 something like <span><strong class="command">CONCAT(Firstname,' ',Surname)</strong></span>
1762 Or, set `identifier:workstations column' to:
1763 <span><strong class="command">NULL</strong></span></p>.
1765 <p>See the MySQL documentation for more language constructs.</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="XMLpassdb"></a>XML</h3></div></div></div><p>
1766 <a class="indexterm" name="id2563196"></a>
1767 <a class="indexterm" name="id2563204"></a>
1768 <a class="indexterm" name="id2563211"></a>
1769 This module requires libxml2 to be installed.</p><p>The usage of pdb_xml is fairly straightforward. To export data, use:
1771 <a class="indexterm" name="id2563227"></a>
1772 <code class="prompt">$ </code> <strong class="userinput"><code>pdbedit -e xml:filename</code></strong>
1774 where filename is the name of the file to put the data in.
1776 To import data, use:
1777 <code class="prompt">$ </code> <strong class="userinput"><code>pdbedit -i xml:filename</code></strong>
1778 </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2563268"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563274"></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="id2563288"></a>passdb backend.
1779 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="id2563306"></a>Users Being Added to the Wrong Backend Database</h3></div></div></div><p>
1780 A few complaints have been received from users who just moved to Samba-3. The following
1781 <code class="filename">smb.conf</code> file entries were causing problems: new accounts were being added to the old
1782 smbpasswd file, not to the tdbsam passdb.tdb file:
1784 </p><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>...</td></tr><tr><td><a class="indexterm" name="id2563345"></a><em class="parameter"><code>passdb backend = smbpasswd, tdbsam</code></em></td></tr><tr><td>...</td></tr></table><p>
1786 Samba will add new accounts to the first entry in the <span class="emphasis"><em>passdb backend</em></span>
1787 parameter entry. If you want to update to the tdbsam, then change the entry to:
1789 </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2563380"></a><em class="parameter"><code>passdb backend = tdbsam, smbpasswd</code></em></td></tr></table><p>
1790 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2563395"></a>Configuration of <em class="parameter"><code>auth methods</code></em></h3></div></div></div><p>
1791 When explicitly setting an <a class="indexterm" name="id2563409"></a>auth methods parameter,
1792 <em class="parameter"><code>guest</code></em> must be specified as the first entry on the line
1793 for example, <a class="indexterm" name="id2563426"></a>auth methods = guest sam.
1794 </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 9. 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 11. Group Mapping: MS Windows and UNIX</td></tr></table></div></body></html>
projects / samba / blob