1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
|
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 11. Account Information Databases</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.4.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="NetworkBrowsing.html" title="Chapter 10. Network Browsing"><link rel="next" href="groupmapping.html" title="Chapter 12. Group Mapping: MS Windows and UNIX"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 11. Account Information Databases</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="groupmapping.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 11. Account Information Databases"><div class="titlepage"><div><div><h2 class="title"><a name="passdb"></a>Chapter 11. Account Information Databases</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span> <div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Olivier (lem)</span> <span class="surname">Lemaire</span></h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>></code></p></div></div></div></div><div><p class="pubdate">May 24, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="passdb.html#id2593316">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2593352">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2593543">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#id2594111">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2594631">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#id2595179">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2595592">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#id2596033">The <code class="literal">smbpasswd</code> Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The <code class="literal">pdbedit</code> Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2598586">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2598639">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2598715">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2598981">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2599139">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2601663">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2601669">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2601707">Configuration of <em class="parameter"><code>auth methods</code></em></a></span></dt></dl></dd></dl></div><p>
<a class="indexterm" name="id2593118"></a>
<a class="indexterm" name="id2593125"></a>
<a class="indexterm" name="id2593132"></a>
<a class="indexterm" name="id2593139"></a>
Early releases of Samba-3 implemented new capability to work concurrently with multiple account backends. This
capability was removed beginning with release of Samba 3.0.23. Commencing with Samba 3.0.23 it is possible to
work with only one specified passwd backend.
</p><p>
<a class="indexterm" name="id2593153"></a>
<a class="indexterm" name="id2593160"></a>
<a class="indexterm" name="id2593167"></a>
<a class="indexterm" name="id2593174"></a>
<a class="indexterm" name="id2593180"></a>
<a class="indexterm" name="id2593187"></a>
The three passdb backends that are fully maintained (actively supported) by the Samba Team are:
<code class="literal">smbpasswd</code> (being obsoleted), <code class="literal">tdbsam</code> (a tdb-based binary file format),
and <code class="literal">ldapsam</code> (LDAP directory). Of these, only the <code class="literal">ldapsam</code> backend
stores both POSIX (UNIX) and Samba user and group account information in a single repository. The
<code class="literal">smbpasswd</code> and <code class="literal">tdbsam</code> backends store only Samba user accounts.
</p><p>
In a strict sense, there are three supported account storage and access systems. One of these is considered
obsolete (smbpasswd). It is recommended to use the <code class="literal">tdbsam</code> method for all simple systems. Use
<code class="literal">ldapsam</code> for larger and more complex networks.
</p><p>
<a class="indexterm" name="id2593258"></a>
<a class="indexterm" name="id2593265"></a>
<a class="indexterm" name="id2593272"></a>
<a class="indexterm" name="id2593279"></a>
<a class="indexterm" name="id2593286"></a>
<a class="indexterm" name="id2593293"></a>
<a class="indexterm" name="id2593300"></a>
In a strict and literal sense, the passdb backends are account storage mechanisms (or methods) alone. The choice
of terminology can be misleading, however we are stuck with this choice of wording. This chapter documents the
nature of the account storage system with a focus on user and trust accounts. Trust accounts have two forms,
machine trust accounts (computer accounts) and interdomain trust accounts. These are all treated as user-like
entities.
</p><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2593316"></a>Features and Benefits</h2></div></div></div><p>
Samba-3 provides for complete backward compatibility with Samba-2.2.x functionality
as follows:
<a class="indexterm" name="id2593325"></a>
<a class="indexterm" name="id2593335"></a>
<a class="indexterm" name="id2593344"></a>
</p><div class="sect2" title="Backward Compatibility Account Storage Systems"><div class="titlepage"><div><div><h3 class="title"><a name="id2593352"></a>Backward Compatibility Account Storage Systems</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Plaintext</span></dt><dd><p>
<a class="indexterm" name="id2593369"></a>
<a class="indexterm" name="id2593376"></a>
<a class="indexterm" name="id2593383"></a>
<a class="indexterm" name="id2593390"></a>
<a class="indexterm" name="id2593397"></a>
This isn't really a backend at all, but is listed here for simplicity. Samba can be configured to pass
plaintext authentication requests to the traditional UNIX/Linux <code class="filename">/etc/passwd</code> and
<code class="filename">/etc/shadow</code>-style subsystems. On systems that have Pluggable Authentication Modules
(PAM) support, all PAM modules are supported. The behavior is just as it was with Samba-2.2.x, and the
protocol limitations imposed by MS Windows clients apply likewise. Please refer to <a class="link" href="passdb.html#passdbtech" title="Technical Information">Technical Information</a>, for more information regarding the limitations of plaintext
password usage.
</p></dd><dt><span class="term">smbpasswd</span></dt><dd><p>
<a class="indexterm" name="id2593444"></a>
<a class="indexterm" name="id2593450"></a>
<a class="indexterm" name="id2593457"></a>
<a class="indexterm" name="id2593464"></a>
This option allows continued use of the <code class="filename">smbpasswd</code>
file that maintains a plain ASCII (text) layout that includes the MS Windows
LanMan and NT-encrypted passwords as well as a field that stores some
account information. This form of password backend does not store any of
the MS Windows NT/200x SAM (Security Account Manager) information required to
provide the extended controls that are needed for more comprehensive
interoperation with MS Windows NT4/200x servers.
</p><p>
This backend should be used only for backward compatibility with older
versions of Samba. It may be deprecated in future releases.
</p></dd><dt><span class="term">ldapsam_compat (Samba-2.2 LDAP Compatibility)</span></dt><dd><p>
<a class="indexterm" name="id2593511"></a>
<a class="indexterm" name="id2593518"></a>
<a class="indexterm" name="id2593525"></a>
There is a password backend option that allows continued operation with
an existing OpenLDAP backend that uses the Samba-2.2.x LDAP schema extension.
This option is provided primarily as a migration tool, although there is
no reason to force migration at this time. This tool will eventually
be deprecated.
</p></dd></dl></div></div><div class="sect2" title="New Account Storage Systems"><div class="titlepage"><div><div><h3 class="title"><a name="id2593543"></a>New Account Storage Systems</h3></div></div></div><p>
Samba-3 introduces a number of new password backend capabilities.
<a class="indexterm" name="id2593552"></a>
<a class="indexterm" name="id2593561"></a>
</p><div class="variablelist"><dl><dt><span class="term">tdbsam</span></dt><dd><p>
<a class="indexterm" name="id2593582"></a>
<a class="indexterm" name="id2593589"></a>
<a class="indexterm" name="id2593596"></a>
This backend provides a rich database backend for local servers. This
backend is not suitable for multiple domain controllers (i.e., PDC + one
or more BDC) installations.
</p><p>
<a class="indexterm" name="id2593609"></a>
<a class="indexterm" name="id2593616"></a>
<a class="indexterm" name="id2593623"></a>
<a class="indexterm" name="id2593630"></a>
<a class="indexterm" name="id2593636"></a>
<a class="indexterm" name="id2593644"></a>
The <span class="emphasis"><em>tdbsam</em></span> password backend stores the old <span class="emphasis"><em>
smbpasswd</em></span> information plus the extended MS Windows NT/200x
SAM information into a binary format TDB (trivial database) file.
The inclusion of the extended information makes it possible for Samba-3
to implement the same account and system access controls that are possible
with MS Windows NT4/200x-based systems.
</p><p>
<a class="indexterm" name="id2593667"></a>
<a class="indexterm" name="id2593674"></a>
<a class="indexterm" name="id2593681"></a>
The inclusion of the <span class="emphasis"><em>tdbsam</em></span> capability is a direct
response to user requests to allow simple site operation without the overhead
of the complexities of running OpenLDAP. It is recommended to use this only
for sites that have fewer than 250 users. For larger sites or implementations,
the use of OpenLDAP or of Active Directory integration is strongly recommended.
</p></dd><dt><span class="term">ldapsam</span></dt><dd><p>
<a class="indexterm" name="id2593709"></a>
<a class="indexterm" name="id2593716"></a>
This provides a rich directory backend for distributed account installation.
</p><p>
<a class="indexterm" name="id2593728"></a>
<a class="indexterm" name="id2593735"></a>
<a class="indexterm" name="id2593742"></a>
<a class="indexterm" name="id2593749"></a>
<a class="indexterm" name="id2593756"></a>
Samba-3 has a new and extended LDAP implementation that requires configuration
of OpenLDAP with a new format Samba schema. The new format schema file is
included in the <code class="filename">examples/LDAP</code> directory of the Samba distribution.
</p><p>
<a class="indexterm" name="id2593778"></a>
<a class="indexterm" name="id2593785"></a>
<a class="indexterm" name="id2593792"></a>
<a class="indexterm" name="id2593798"></a>
<a class="indexterm" name="id2593806"></a>
The new LDAP implementation significantly expands the control abilities that
were possible with prior versions of Samba. It is now possible to specify
<span class="quote">“<span class="quote">per-user</span>”</span> profile settings, home directories, account access controls, and
much more. Corporate sites will see that the Samba Team has listened to their
requests both for capability and greater scalability.
</p></dd></dl></div></div></div><div class="sect1" title="Technical Information"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="passdbtech"></a>Technical Information</h2></div></div></div><p>
<a class="indexterm" name="id2593840"></a>
<a class="indexterm" name="id2593847"></a>
Old Windows clients send plaintext passwords over the wire. Samba can check these
passwords by encrypting them and comparing them to the hash stored in the UNIX user database.
</p><p>
<a class="indexterm" name="id2593860"></a>
<a class="indexterm" name="id2593867"></a>
<a class="indexterm" name="id2593874"></a>
<a class="indexterm" name="id2593881"></a>
Newer Windows clients send encrypted passwords (LanMan and NT hashes) instead of plaintext passwords over
the wire. The newest clients will send only encrypted passwords and refuse to send plaintext passwords unless
their registry is tweaked.
</p><p>
<a class="indexterm" name="id2593895"></a>
<a class="indexterm" name="id2593902"></a>
Many people ask why Samba cannot simply use the UNIX password database. Windows requires
passwords that are encrypted in its own format. The UNIX passwords can't be converted to
UNIX-style encrypted passwords. Because of that, you can't use the standard UNIX user
database, and you have to store the LanMan and NT hashes somewhere else.
</p><p>
<a class="indexterm" name="id2593918"></a>
<a class="indexterm" name="id2593925"></a>
<a class="indexterm" name="id2593932"></a>
<a class="indexterm" name="id2593939"></a>
In addition to differently encrypted passwords, Windows also stores certain data for each
user that is not stored in a UNIX user database: for example, workstations the user may logon from,
the location where the user's profile is stored, and so on. Samba retrieves and stores this
information using a <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>. Commonly available backends are LDAP,
tdbsam, and plain text file. For more information, see the man page for <code class="filename">smb.conf</code> regarding the
<a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a> parameter.
</p><div class="figure"><a name="idmap-sid2uid"></a><p class="title"><b>Figure 11.1. IDMAP: Resolution of SIDs to UIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-sid2uid.png" width="216" alt="IDMAP: Resolution of SIDs to UIDs."></div></div></div><br class="figure-break"><p>
<a class="indexterm" name="id2594028"></a>
<a class="indexterm" name="id2594035"></a>
<a class="indexterm" name="id2594042"></a>
The resolution of SIDs to UIDs is fundamental to correct operation of Samba. In both cases shown, if winbindd
is not running or cannot be contacted, then only local SID/UID resolution is possible. See <a class="link" href="passdb.html#idmap-sid2uid" title="Figure 11.1. IDMAP: Resolution of SIDs to UIDs.">resolution of SIDs to UIDs</a> and <a class="link" href="passdb.html#idmap-uid2sid" title="Figure 11.2. IDMAP: Resolution of UIDs to SIDs.">resolution of UIDs
to SIDs</a> diagrams.
</p><div class="figure"><a name="idmap-uid2sid"></a><p class="title"><b>Figure 11.2. IDMAP: Resolution of UIDs to SIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-uid2sid.png" width="270" alt="IDMAP: Resolution of UIDs to SIDs."></div></div></div><br class="figure-break"><div class="sect2" title="Important Notes About Security"><div class="titlepage"><div><div><h3 class="title"><a name="id2594111"></a>Important Notes About Security</h3></div></div></div><p>
<a class="indexterm" name="id2594119"></a>
<a class="indexterm" name="id2594126"></a>
<a class="indexterm" name="id2594133"></a>
<a class="indexterm" name="id2594140"></a>
<a class="indexterm" name="id2594147"></a>
The UNIX and SMB password encryption techniques seem similar on the surface. This
similarity is, however, only skin deep. The UNIX scheme typically sends clear-text
passwords over the network when logging in. This is bad. The SMB encryption scheme
never sends the clear-text password over the network, but it does store the 16-byte
hashed values on disk. This is also bad. Why? Because the 16 byte hashed values
are a <span class="quote">“<span class="quote">password equivalent.</span>”</span> You cannot derive the user's password from them, but
they could potentially be used in a modified client to gain access to a server.
This would require considerable technical knowledge on behalf of the attacker but
is perfectly possible. You should therefore treat the data stored in whatever passdb
backend you use (smbpasswd file, LDAP) as though it contained the clear-text
passwords of all your users. Its contents must be kept secret, and the file should
be protected accordingly.
</p><p>
<a class="indexterm" name="id2594177"></a>
<a class="indexterm" name="id2594183"></a>
<a class="indexterm" name="id2594190"></a>
Ideally, we would like a password scheme that involves neither plaintext passwords
on the network nor plaintext passwords on disk. Unfortunately, this is not available because Samba is stuck with
having to be compatible with other SMB systems (Windows NT, Windows for Workgroups, Windows 9x/Me).
</p><p>
<a class="indexterm" name="id2594205"></a>
<a class="indexterm" name="id2594212"></a>
Windows NT 4.0 Service Pack 3 changed the default setting so plaintext passwords
are disabled from being sent over the wire. This mandates either the use of encrypted
password support or editing the Windows NT registry to re-enable plaintext passwords.
</p><p>
<a class="indexterm" name="id2594226"></a>
<a class="indexterm" name="id2594233"></a>
The following versions of Microsoft Windows do not support full domain security protocols,
although they may log onto a domain environment:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>MS DOS Network client 3.0 with the basic network redirector installed.</p></li><li class="listitem"><p>Windows 95 with the network redirector update installed.</p></li><li class="listitem"><p>Windows 98 [Second Edition].</p></li><li class="listitem"><p>Windows Me.</p></li></ul></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
<a class="indexterm" name="id2594272"></a>
<a class="indexterm" name="id2594279"></a>
<a class="indexterm" name="id2594286"></a>
MS Windows XP Home does not have facilities to become a domain member, and it cannot participate in domain logons.
</p></div><p>
The following versions of MS Windows fully support domain security protocols.
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Windows NT 3.5x.</p></li><li class="listitem"><p>Windows NT 4.0.</p></li><li class="listitem"><p>Windows 2000 Professional.</p></li><li class="listitem"><p>Windows 200x Server/Advanced Server.</p></li><li class="listitem"><p>Windows XP Professional.</p></li></ul></div><p>
<a class="indexterm" name="id2594331"></a>
<a class="indexterm" name="id2594338"></a>
<a class="indexterm" name="id2594345"></a>
<a class="indexterm" name="id2594352"></a>
<a class="indexterm" name="id2594358"></a>
<a class="indexterm" name="id2594365"></a>
All current releases of Microsoft SMB/CIFS clients support authentication via the
SMB challenge/response mechanism described here. Enabling clear-text authentication
does not disable the ability of the client to participate in encrypted authentication.
Instead, it allows the client to negotiate either plaintext or encrypted password
handling.
</p><p>
<a class="indexterm" name="id2594381"></a>
<a class="indexterm" name="id2594388"></a>
<a class="indexterm" name="id2594395"></a>
<a class="indexterm" name="id2594402"></a>
<a class="indexterm" name="id2594409"></a>
MS Windows clients will cache the encrypted password alone. Where plaintext passwords
are re-enabled through the appropriate registry change, the plaintext password is never
cached. This means that in the event that a network connections should become disconnected
(broken), only the cached (encrypted) password will be sent to the resource server to
effect an auto-reconnect. If the resource server does not support encrypted passwords, the
auto-reconnect will fail. Use of encrypted passwords is strongly advised.
</p><div class="sect3" title="Advantages of Encrypted Passwords"><div class="titlepage"><div><div><h4 class="title"><a name="id2594426"></a>Advantages of Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
<a class="indexterm" name="id2594438"></a>
<a class="indexterm" name="id2594445"></a>
<a class="indexterm" name="id2594452"></a>
Plaintext passwords are not passed across the network. Someone using a network sniffer
cannot just record passwords going to the SMB server.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2594465"></a>
<a class="indexterm" name="id2594472"></a>
<a class="indexterm" name="id2594479"></a>
Plaintext passwords are not stored anywhere in memory or on disk.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2594491"></a>
<a class="indexterm" name="id2594498"></a>
<a class="indexterm" name="id2594505"></a>
<a class="indexterm" name="id2594512"></a>
Windows NT does not like talking to a server that does not support encrypted passwords. It will refuse to
browse the server if the server is also in user-level security mode. It will insist on prompting the user for
the password on each connection, which is very annoying. The only thing you can do to stop this is to use SMB
encryption.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2594530"></a>
<a class="indexterm" name="id2594536"></a>
Encrypted password support allows automatic share (resource) reconnects.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2594549"></a>
<a class="indexterm" name="id2594556"></a>
Encrypted passwords are essential for PDC/BDC operation.
</p></li></ul></div></div><div class="sect3" title="Advantages of Non-Encrypted Passwords"><div class="titlepage"><div><div><h4 class="title"><a name="id2594567"></a>Advantages of Non-Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
<a class="indexterm" name="id2594578"></a>
Plaintext passwords are not kept on disk and are not cached in memory.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2594591"></a>
<a class="indexterm" name="id2594598"></a>
Plaintext passwords use the same password file as other UNIX services, such as Login and FTP.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2594610"></a>
<a class="indexterm" name="id2594617"></a>
Use of other services (such as Telnet and FTP) that send plaintext passwords over
the network makes sending them for SMB not such a big deal.
</p></li></ul></div></div></div><div class="sect2" title="Mapping User Identifiers between MS Windows and UNIX"><div class="titlepage"><div><div><h3 class="title"><a name="id2594631"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div></div><p>
<a class="indexterm" name="id2594639"></a>
<a class="indexterm" name="id2594646"></a>
<a class="indexterm" name="id2594652"></a>
Every operation in UNIX/Linux requires a user identifier (UID), just as in
MS Windows NT4/200x this requires a security identifier (SID). Samba provides
two means for mapping an MS Windows user to a UNIX/Linux UID.
</p><p>
<a class="indexterm" name="id2594666"></a>
<a class="indexterm" name="id2594673"></a>
<a class="indexterm" name="id2594679"></a>
<a class="indexterm" name="id2594686"></a>
<a class="indexterm" name="id2594693"></a>
First, all Samba SAM database accounts require a UNIX/Linux UID that the account will map to. As users are
added to the account information database, Samba will call the <a class="link" href="smb.conf.5.html#ADDUSERSCRIPT" target="_top">add user script</a>
interface to add the account to the Samba host OS. In essence all accounts in the local SAM require a local
user account.
</p><p>
<a class="indexterm" name="id2594722"></a>
<a class="indexterm" name="id2594728"></a>
<a class="indexterm" name="id2594735"></a>
<a class="indexterm" name="id2594742"></a>
<a class="indexterm" name="id2594748"></a>
<a class="indexterm" name="id2594754"></a>
<a class="indexterm" name="id2594762"></a>
The second way to map Windows SID to UNIX UID is via the <span class="emphasis"><em>idmap uid</em></span> and
<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
these parameters. These parameters are essential when mapping users from a remote (non-member Windows client
or a member of a foreign domain) SAM server.
</p></div><div class="sect2" title="Mapping Common UIDs/GIDs on Distributed Machines"><div class="titlepage"><div><div><h3 class="title"><a name="idmapbackend"></a>Mapping Common UIDs/GIDs on Distributed Machines</h3></div></div></div><p>
<a class="indexterm" name="id2594801"></a>
<a class="indexterm" name="id2594807"></a>
<a class="indexterm" name="id2594814"></a>
<a class="indexterm" name="id2594820"></a>
<a class="indexterm" name="id2594828"></a>
<a class="indexterm" name="id2594834"></a>
Samba-3 has a special facility that makes it possible to maintain identical UIDs and GIDs
on all servers in a distributed network. A distributed network is one where there exists
a PDC, one or more BDCs, and/or one or more domain member servers. Why is this important?
This is important if files are being shared over more than one protocol (e.g., NFS) and where
users are copying files across UNIX/Linux systems using tools such as <code class="literal">rsync</code>.
</p><p>
<a class="indexterm" name="id2594857"></a>
<a class="indexterm" name="id2594864"></a>
<a class="indexterm" name="id2594871"></a>
<a class="indexterm" name="id2594877"></a>
<a class="indexterm" name="id2594884"></a>
<a class="indexterm" name="id2594890"></a>
<a class="indexterm" name="id2594897"></a>
<a class="indexterm" name="id2594904"></a>
The special facility is enabled using a parameter called <em class="parameter"><code>idmap backend</code></em>.
The default setting for this parameter is an empty string. Technically it is possible to use
an LDAP-based idmap backend for UIDs and GIDs, but it makes most sense when this is done for
network configurations that also use LDAP for the SAM backend.
<a class="link" href="passdb.html#idmapbackendexample" title="Example 11.1. Example Configuration with the LDAP idmap Backend">Example Configuration with the LDAP idmap Backend</a>
shows that configuration.
</p><a class="indexterm" name="id2594933"></a><div class="example"><a name="idmapbackendexample"></a><p class="title"><b>Example 11.1. Example Configuration with the LDAP idmap Backend</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2594967"></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="id2594983"></a><em class="parameter"><code>idmap backend = ldap:ldaps://ldap-server.quenya.org</code></em></td></tr></table></div></div><br class="example-break"><p>
<a class="indexterm" name="id2594999"></a>
<a class="indexterm" name="id2595006"></a>
A network administrator who wants to make significant use of LDAP backends will sooner or later be
exposed to the excellent work done by PADL Software. PADL <a class="ulink" href="http://www.padl.com" target="_top">http://www.padl.com</a> have
produced and released to open source an array of tools that might be of interest. These tools include:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
<a class="indexterm" name="id2595029"></a>
<a class="indexterm" name="id2595036"></a>
<a class="indexterm" name="id2595043"></a>
<a class="indexterm" name="id2595050"></a>
<a class="indexterm" name="id2595056"></a>
<a class="indexterm" name="id2595063"></a>
<a class="indexterm" name="id2595070"></a>
<a class="indexterm" name="id2595076"></a>
<span class="emphasis"><em>nss_ldap:</em></span> An LDAP name service switch (NSS) module to provide native
name service support for AIX, Linux, Solaris, and other operating systems. This tool
can be used for centralized storage and retrieval of UIDs and GIDs.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2595097"></a>
<a class="indexterm" name="id2595103"></a>
<a class="indexterm" name="id2595110"></a>
<a class="indexterm" name="id2595117"></a>
<span class="emphasis"><em>pam_ldap:</em></span> A PAM module that provides LDAP integration for UNIX/Linux
system access authentication.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2595135"></a>
<a class="indexterm" name="id2595142"></a>
<a class="indexterm" name="id2595149"></a>
<a class="indexterm" name="id2595156"></a>
<span class="emphasis"><em>idmap_ad:</em></span> An IDMAP backend that supports the Microsoft Services for
UNIX RFC 2307 schema available from the PADL Web
<a class="ulink" href="http://www.padl.com/download/xad_oss_plugins.tar.gz" target="_top">site</a>.
</p></li></ul></div></div><div class="sect2" title="Comments Regarding LDAP"><div class="titlepage"><div><div><h3 class="title"><a name="id2595179"></a>Comments Regarding LDAP</h3></div></div></div><p>
<a class="indexterm" name="id2595187"></a>
<a class="indexterm" name="id2595196"></a>
<a class="indexterm" name="id2595203"></a>
<a class="indexterm" name="id2595210"></a>
There is much excitement and interest in LDAP directories in the information technology world
today. The LDAP architecture was designed to be highly scalable. It was also designed for
use across a huge number of potential areas of application encompassing a wide range of operating
systems and platforms. LDAP technologies are at the heart of the current generations of Federated
Identity Management (FIM) solutions that can underlie a corporate Single Sign-On (SSO) environment.
</p><p>
<a class="indexterm" name="id2595228"></a>
<a class="indexterm" name="id2595235"></a>
<a class="indexterm" name="id2595241"></a>
<a class="indexterm" name="id2595248"></a>
LDAP implementations have been built across a wide variety of platforms. It lies at the core of Microsoft
Windows Active Directory services (ADS), Novell's eDirectory, as well as many others. Implementation of the
directory services LDAP involves interaction with legacy as well as new generation applications, all of which
depend on some form of authentication services.
</p><p>
<a class="indexterm" name="id2595264"></a>
<a class="indexterm" name="id2595271"></a>
<a class="indexterm" name="id2595278"></a>
<a class="indexterm" name="id2595285"></a>
<a class="indexterm" name="id2595292"></a>
<a class="indexterm" name="id2595299"></a>
<a class="indexterm" name="id2595306"></a>
<a class="indexterm" name="id2595313"></a>
<a class="indexterm" name="id2595320"></a>
<a class="indexterm" name="id2595327"></a>
<a class="indexterm" name="id2595334"></a>
<a class="indexterm" name="id2595340"></a>
<a class="indexterm" name="id2595347"></a>
<a class="indexterm" name="id2595354"></a>
UNIX services can utilize LDAP directory information for authentication and access controls
through intermediate tools and utilities. The total environment that consists of the LDAP directory
and the middle-ware tools and utilities makes it possible for all user access to the UNIX platform
to be managed from a central environment and yet distributed to wherever the point of need may
be physically located. Applications that benefit from this infrastructure include: UNIX login
shells, mail and messaging systems, quota controls, printing systems, DNS servers, DHCP servers,
and also Samba.
</p><p>
<a class="indexterm" name="id2595374"></a>
<a class="indexterm" name="id2595381"></a>
<a class="indexterm" name="id2595388"></a>
<a class="indexterm" name="id2595395"></a>
<a class="indexterm" name="id2595402"></a>
<a class="indexterm" name="id2595409"></a>
Many sites are installing LDAP for the first time in order to provide a scalable passdb backend
for Samba. Others are faced with the need to adapt an existing LDAP directory to new uses such
as for the Samba SAM backend. Whatever your particular need and attraction to Samba may be,
decisions made in respect of the design of the LDAP directory structure and its implementation
are of a durable nature for the site. These have far-reaching implications that affect long-term
information systems management costs.
</p><p>
<a class="indexterm" name="id2595428"></a>
<a class="indexterm" name="id2595435"></a>
Do not rush into an LDAP deployment. Take the time to understand how the design of the Directory
Information Tree (DIT) may impact current and future site needs, as well as the ability to meet
them. The way that Samba SAM information should be stored within the DIT varies from site to site
and with each implementation new experience is gained. It is well understood by LDAP veterans that
first implementations create awakening, second implementations of LDAP create fear, and
third-generation deployments bring peace and tranquility.
</p><div class="sect3" title="Caution Regarding LDAP and Samba"><div class="titlepage"><div><div><h4 class="title"><a name="id2595454"></a>Caution Regarding LDAP and Samba</h4></div></div></div><p>
<a class="indexterm" name="id2595463"></a>
<a class="indexterm" name="id2595470"></a>
<a class="indexterm" name="id2595477"></a>
<a class="indexterm" name="id2595484"></a>
<a class="indexterm" name="id2595490"></a>
<a class="indexterm" name="id2595498"></a>
<a class="indexterm" name="id2595505"></a>
Samba requires UNIX POSIX identity information as well as a place to store information that is
specific to Samba and the Windows networking environment. The most used information that must
be dealt with includes: user accounts, group accounts, machine trust accounts, interdomain
trust accounts, and intermediate information specific to Samba internals.
</p><p>
<a class="indexterm" name="id2595521"></a>
<a class="indexterm" name="id2595528"></a>
<a class="indexterm" name="id2595535"></a>
The example deployment guidelines in this book, as well as other books and HOWTO documents
available from the internet may not fit with established directory designs and implementations.
The existing DIT may not be able to accommodate the simple information layout proposed in common
sources. Additionally, you may find that the common scripts and tools that are used to provision
the LDAP directory for use with Samba may not suit your needs.
</p><p>
<a class="indexterm" name="id2595553"></a>
It is not uncommon, for sites that have existing LDAP DITs to find necessity to generate a
set of site-specific scripts and utilities to make it possible to deploy Samba within the
scope of site operations. The way that user and group accounts are distributed throughout
the DIT may make this a challenging matter. The solution will, of course, be rewarding, but
the journey to it may be challenging. Take time to understand site needs and do not rush
into deployment.
</p><p>
<a class="indexterm" name="id2595571"></a>
<a class="indexterm" name="id2595578"></a>
Above all, do not blindly use scripts and tools that are not suitable for your site. Check
and validate all scripts before you execute them to make sure that the existing infrastructure
will not be damaged by inadvertent use of an inappropriate tool.
</p></div></div><div class="sect2" title="LDAP Directories and Windows Computer Accounts"><div class="titlepage"><div><div><h3 class="title"><a name="id2595592"></a>LDAP Directories and Windows Computer Accounts</h3></div></div></div><p>
<a class="indexterm" name="id2595600"></a>
<a class="indexterm" name="id2595607"></a>
<a class="indexterm" name="id2595614"></a>
Samba doesn't provide a turnkey solution to LDAP. It is best to deal with the design and
configuration of an LDAP directory prior to integration with Samba. A working knowledge
of LDAP makes Samba integration easy, and the lack of a working knowledge of LDAP can make
it a frustrating experience.
</p><p>
<a class="indexterm" name="id2595630"></a>
<a class="indexterm" name="id2595637"></a>
<a class="indexterm" name="id2595644"></a>
Computer (machine) accounts can be placed wherever you like in an LDAP directory subject
to some constraints that are described in this chapter.
</p><p>
<a class="indexterm" name="id2595656"></a>
<a class="indexterm" name="id2595663"></a>
<a class="indexterm" name="id2595670"></a>
<a class="indexterm" name="id2595677"></a>
<a class="indexterm" name="id2595684"></a>
<a class="indexterm" name="id2595691"></a>
<a class="indexterm" name="id2595698"></a>
The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba.
Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats
them. A user account and a machine account are indistinguishable from each other, except that
the machine account ends in a $ character, as do trust accounts.
</p><p>
<a class="indexterm" name="id2595714"></a>
<a class="indexterm" name="id2595721"></a>
<a class="indexterm" name="id2595728"></a>
<a class="indexterm" name="id2595734"></a>
<a class="indexterm" name="id2595741"></a>
The need for Windows user, group, machine, trust, and other accounts to be tied to a valid UNIX
UID is a design decision that was made a long way back in the history of Samba development. It
is unlikely that this decision will be reversed or changed during the remaining life of the
Samba-3.x series.
</p><p>
<a class="indexterm" name="id2595756"></a>
<a class="indexterm" name="id2595763"></a>
<a class="indexterm" name="id2595769"></a>
The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that
must refer back to the host operating system on which Samba is running. The NSS is the preferred
mechanism that shields applications (like Samba) from the need to know everything about every
host OS it runs on.
</p><p>
<a class="indexterm" name="id2595785"></a>
<a class="indexterm" name="id2595791"></a>
<a class="indexterm" name="id2595798"></a>
<a class="indexterm" name="id2595805"></a>
<a class="indexterm" name="id2595812"></a>
<a class="indexterm" name="id2595818"></a>
<a class="indexterm" name="id2595825"></a>
Samba asks the host OS to provide a UID via the <span class="quote">“<span class="quote">passwd</span>”</span>, <span class="quote">“<span class="quote">shadow</span>”</span>,
and <span class="quote">“<span class="quote">group</span>”</span> facilities in the NSS control (configuration) file. The best tool
for achieving this is left up to the UNIX administrator to determine. It is not imposed by
Samba. Samba provides winbindd with its support libraries as one method. It is
possible to do this via LDAP, and for that Samba provides the appropriate hooks so that
all account entities can be located in an LDAP directory.
</p><p>
<a class="indexterm" name="id2595853"></a>
<a class="indexterm" name="id2595860"></a>
<a class="indexterm" name="id2595867"></a>
<a class="indexterm" name="id2595873"></a>
<a class="indexterm" name="id2595880"></a>
For many the weapon of choice is to use the PADL nss_ldap utility. This utility must
be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That
is fundamentally an LDAP design question. The information provided on the Samba list and
in the documentation is directed at providing working examples only. The design
of an LDAP directory is a complex subject that is beyond the scope of this documentation.
</p></div></div><div class="sect1" title="Account Management Tools"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="acctmgmttools"></a>Account Management Tools</h2></div></div></div><p>
<a class="indexterm" name="id2595910"></a>
<a class="indexterm" name="id2595917"></a>
<a class="indexterm" name="id2595924"></a>
Samba provides two tools for management of user and machine accounts:
<code class="literal">smbpasswd</code> and <code class="literal">pdbedit</code>.
</p><p>
<a class="indexterm" name="id2595947"></a>
<a class="indexterm" name="id2595954"></a>
<a class="indexterm" name="id2595961"></a>
The <code class="literal">pdbedit</code> can be used to manage account policies in addition to
Samba user account information. The policy management capability is used to administer
domain default settings for password aging and management controls to handle failed login
attempts.
</p><p>
<a class="indexterm" name="id2595981"></a>
<a class="indexterm" name="id2595988"></a>
<a class="indexterm" name="id2595995"></a>
<a class="indexterm" name="id2596002"></a>
Some people are confused when reference is made to <code class="literal">smbpasswd</code> because the
name refers to a storage mechanism for SambaSAMAccount information, but it is also the name
of a utility tool. That tool is destined to eventually be replaced by new functionality that
is being added to the <code class="literal">net</code> toolset (see <a class="link" href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command">the Net Command</a>.
</p><div class="sect2" title="The smbpasswd Tool"><div class="titlepage"><div><div><h3 class="title"><a name="id2596033"></a>The <code class="literal">smbpasswd</code> Tool</h3></div></div></div><p>
<a class="indexterm" name="id2596046"></a>
<a class="indexterm" name="id2596053"></a>
<a class="indexterm" name="id2596060"></a>
<a class="indexterm" name="id2596067"></a>
<a class="indexterm" name="id2596074"></a>
The <code class="literal">smbpasswd</code> utility is similar to the <code class="literal">passwd</code>
and <code class="literal">yppasswd</code> programs. It maintains the two 32 byte password
fields in the passdb backend. This utility operates independently of the actual
account and password storage methods used (as specified by the <em class="parameter"><code>passdb
backend</code></em> in the <code class="filename">smb.conf</code> file.
</p><p>
<a class="indexterm" name="id2596118"></a>
<a class="indexterm" name="id2596124"></a>
<code class="literal">smbpasswd</code> works in a client-server mode where it contacts the
local smbd to change the user's password on its behalf. This has enormous benefits.
</p><p>
<a class="indexterm" name="id2596143"></a>
<a class="indexterm" name="id2596150"></a>
<code class="literal">smbpasswd</code> has the capability to change passwords on Windows NT
servers (this only works when the request is sent to the NT PDC if changing an NT
domain user's password).
</p><p>
<a class="indexterm" name="id2596168"></a>
<a class="indexterm" name="id2596175"></a>
<code class="literal">smbpasswd</code> can be used to:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>add</em></span> user or machine accounts.</p></li><li class="listitem"><p><span class="emphasis"><em>delete</em></span> user or machine accounts.</p></li><li class="listitem"><p><span class="emphasis"><em>enable</em></span> user or machine accounts.</p></li><li class="listitem"><p><span class="emphasis"><em>disable</em></span> user or machine accounts.</p></li><li class="listitem"><p><span class="emphasis"><em>set to NULL</em></span> user passwords.</p></li><li class="listitem"><p><span class="emphasis"><em>manage</em></span> interdomain trust accounts.</p></li></ul></div><p>
To run smbpasswd as a normal user, just type:
</p><p>
</p><pre class="screen">
<code class="prompt">$ </code><strong class="userinput"><code>smbpasswd</code></strong>
<code class="prompt">Old SMB password: </code><strong class="userinput"><code><em class="replaceable"><code>secret</code></em></code></strong>
</pre><p>
For <em class="replaceable"><code>secret</code></em>, type the old value here or press return if
there is no old password.
</p><pre class="screen">
<code class="prompt">New SMB Password: </code><strong class="userinput"><code><em class="replaceable"><code>new secret</code></em></code></strong>
<code class="prompt">Repeat New SMB Password: </code><strong class="userinput"><code><em class="replaceable"><code>new secret</code></em></code></strong>
</pre><p>
</p><p>
If the old value does not match the current value stored for that user, or the two
new values do not match each other, then the password will not be changed.
</p><p>
<a class="indexterm" name="id2596316"></a>
When invoked by an ordinary user, the command will allow only the user to change his or her own
SMB password.
</p><p>
<a class="indexterm" name="id2596328"></a>
<a class="indexterm" name="id2596335"></a>
When run by root, <code class="literal">smbpasswd</code> may take an optional argument specifying
the username whose SMB password you wish to change. When run as root, <code class="literal">smbpasswd</code>
does not prompt for or check the old password value, thus allowing root to set passwords
for users who have forgotten their passwords.
</p><p>
<a class="indexterm" name="id2596361"></a>
<a class="indexterm" name="id2596368"></a>
<a class="indexterm" name="id2596375"></a>
<a class="indexterm" name="id2596382"></a>
<code class="literal">smbpasswd</code> is designed to work in the way familiar to UNIX
users who use the <code class="literal">passwd</code> or <code class="literal">yppasswd</code> commands.
While designed for administrative use, this tool provides essential user-level
password change capabilities.
</p><p>
<a class="indexterm" name="id2596413"></a>
For more details on using <code class="literal">smbpasswd</code>, refer to the man page (the
definitive reference).
</p></div><div class="sect2" title="The pdbedit Tool"><div class="titlepage"><div><div><h3 class="title"><a name="pdbeditthing"></a>The <code class="literal">pdbedit</code> Tool</h3></div></div></div><p>
<a class="indexterm" name="id2596447"></a>
<a class="indexterm" name="id2596454"></a>
<a class="indexterm" name="id2596461"></a>
<a class="indexterm" name="id2596468"></a>
<code class="literal">pdbedit</code> is a tool that can be used only by root. It is used to
manage the passdb backend, as well as domain-wide account policy settings. <code class="literal">pdbedit</code>
can be used to:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>add, remove, or modify user accounts.</p></li><li class="listitem"><p>list user accounts.</p></li><li class="listitem"><p>migrate user accounts.</p></li><li class="listitem"><p>migrate group accounts.</p></li><li class="listitem"><p>manage account policies.</p></li><li class="listitem"><p>manage domain access policy settings.</p></li></ul></div><p>
<a class="indexterm" name="id2596527"></a>
Under the terms of the Sarbanes-Oxley Act of 2002, American businesses and organizations are mandated to
implement a series of <code class="literal">internal controls</code> and procedures to communicate, store,
and protect financial data. The Sarbanes-Oxley Act has far reaching implications in respect of:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Who has access to information systems that store financial data.</p></li><li class="listitem"><p>How personal and financial information is treated among employees and business
partners.</p></li><li class="listitem"><p>How security vulnerabilities are managed.</p></li><li class="listitem"><p>Security and patch level maintenance for all information systems.</p></li><li class="listitem"><p>How information systems changes are documented and tracked.</p></li><li class="listitem"><p>How information access controls are implemented and managed.</p></li><li class="listitem"><p>Auditability of all information systems in respect of change and security.</p></li><li class="listitem"><p>Disciplinary procedures and controls to ensure privacy.</p></li></ol></div><p>
<a class="indexterm" name="id2596599"></a>
<a class="indexterm" name="id2596606"></a>
In short, the Sarbanes-Oxley Act of 2002 is an instrument that enforces accountability in respect of
business related information systems so as to ensure the compliance of all information systems that
are used to store personal information and particularly for financial records processing. Similar
accountabilities are being demanded around the world.
</p><p>
<a class="indexterm" name="id2596628"></a>
<a class="indexterm" name="id2596635"></a>
<a class="indexterm" name="id2596642"></a>
<a class="indexterm" name="id2596649"></a>
<a class="indexterm" name="id2596656"></a>
The need to be familiar with the Samba tools and facilities that permit information systems operation
in compliance with government laws and regulations is clear to all. The <code class="literal">pdbedit</code> is
currently the only Samba tool that provides the capacity to manage account and systems access controls
and policies. During the remaining life-cycle of the Samba-3 series it is possible the new tools may
be implemented to aid in this important area.
</p><p>
Domain global policy controls available in Windows NT4 compared with Samba
is shown in <a class="link" href="passdb.html#policycontrols" title="Table 11.1. NT4 Domain v's Samba Policy Controls">NT4 Domain v's Samba Policy Controls</a>.
</p><div class="table"><a name="policycontrols"></a><p class="title"><b>Table 11.1. NT4 Domain v's Samba Policy Controls</b></p><div class="table-contents"><table summary="NT4 Domain v's Samba Policy Controls" border="1"><colgroup><col align="left"><col align="left"><col align="center"><col align="center"><col align="center"></colgroup><thead><tr><th align="left"><p>NT4 policy Name</p></th><th align="left"><p>Samba Policy Name</p></th><th align="center"><p>NT4 Range</p></th><th align="center"><p>Samba Range</p></th><th align="center"><p>Samba Default</p></th></tr></thead><tbody><tr><td align="left"><p>Maximum Password Age</p></td><td align="left"><p>maximum password age</p></td><td align="center"><p>0 - 999 (days)</p></td><td align="center"><p>0 - 4294967295 (sec)</p></td><td align="center"><p>4294967295</p></td></tr><tr><td align="left"><p>Minimum Password Age</p></td><td align="left"><p>minimum password age</p></td><td align="center"><p>0 - 999 (days)</p></td><td align="center"><p>0 - 4294967295 (sec)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Minimum Password Length</p></td><td align="left"><p>min password length</p></td><td align="center"><p>1 - 14 (Chars)</p></td><td align="center"><p>0 - 4294967295 (Chars)</p></td><td align="center"><p>5</p></td></tr><tr><td align="left"><p>Password Uniqueness</p></td><td align="left"><p>password history</p></td><td align="center"><p>0 - 23 (#)</p></td><td align="center"><p>0 - 4294967295 (#)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Account Lockout - Reset count after</p></td><td align="left"><p>reset count minutes</p></td><td align="center"><p>1 - 99998 (min)</p></td><td align="center"><p>0 - 4294967295 (min)</p></td><td align="center"><p>30</p></td></tr><tr><td align="left"><p>Lockout after bad logon attempts</p></td><td align="left"><p>bad lockout attempt</p></td><td align="center"><p>0 - 998 (#)</p></td><td align="center"><p>0 - 4294967295 (#)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>*** Not Known ***</p></td><td align="left"><p>disconnect time</p></td><td align="center"><p>TBA</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Lockout Duration</p></td><td align="left"><p>lockout duration</p></td><td align="center"><p>1 - 99998 (min)</p></td><td align="center"><p>0 - 4294967295 (min)</p></td><td align="center"><p>30</p></td></tr><tr><td align="left"><p>Users must log on in order to change password</p></td><td align="left"><p>user must logon to change password</p></td><td align="center"><p>0/1</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>*** Registry Setting ***</p></td><td align="left"><p>refuse machine password change</p></td><td align="center"><p>0/1</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr></tbody></table></div></div><br class="table-break"><p>
<a class="indexterm" name="id2597039"></a>
<a class="indexterm" name="id2597046"></a>
<a class="indexterm" name="id2597053"></a>
<a class="indexterm" name="id2597060"></a>
The <code class="literal">pdbedit</code> tool is the only one that can manage the account
security and policy settings. It is capable of all operations that smbpasswd can
do as well as a superset of them.
</p><p>
<a class="indexterm" name="id2597078"></a>
<a class="indexterm" name="id2597085"></a>
<a class="indexterm" name="id2597092"></a>
One particularly important purpose of the <code class="literal">pdbedit</code> is to allow
the import/export of account information from one passdb backend to another.
</p><div class="sect3" title="User Account Management"><div class="titlepage"><div><div><h4 class="title"><a name="id2597109"></a>User Account Management</h4></div></div></div><p>
<a class="indexterm" name="id2597117"></a>
<a class="indexterm" name="id2597124"></a>
<a class="indexterm" name="id2597130"></a>
<a class="indexterm" name="id2597137"></a>
<a class="indexterm" name="id2597144"></a>
<a class="indexterm" name="id2597151"></a>
<a class="indexterm" name="id2597158"></a>
The <code class="literal">pdbedit</code> tool, like the <code class="literal">smbpasswd</code> tool, requires
that a POSIX user account already exists in the UNIX/Linux system accounts database (backend).
Neither tool will call out to the operating system to create a user account because this is
considered to be the responsibility of the system administrator. When the Windows NT4 domain
user manager is used to add an account, Samba will implement the <code class="literal">add user script</code>
(as well as the other interface scripts) to ensure that user, group and machine accounts are
correctly created and changed. The use of the <code class="literal">pdbedit</code> tool does not
make use of these interface scripts.
</p><p>
<a class="indexterm" name="id2597202"></a>
<a class="indexterm" name="id2597209"></a>
Before attempting to use the <code class="literal">pdbedit</code> tool to manage user and machine
accounts, make certain that a system (POSIX) account has already been created.
</p><div class="sect4" title="Listing User and Machine Accounts"><div class="titlepage"><div><div><h5 class="title"><a name="id2597225"></a>Listing User and Machine Accounts</h5></div></div></div><p>
<a class="indexterm" name="id2597233"></a>
<a class="indexterm" name="id2597240"></a>
The following is an example of the user account information that is stored in
a tdbsam password backend. This listing was produced by running:
</p><pre class="screen">
<code class="prompt">$ </code><strong class="userinput"><code>pdbedit -Lv met</code></strong>
UNIX username: met
NT username: met
Account Flags: [U ]
User SID: S-1-5-21-1449123459-1407424037-3116680435-2004
Primary Group SID: S-1-5-21-1449123459-1407424037-3116680435-1201
Full Name: Melissa E Terpstra
Home Directory: \\frodo\met\Win9Profile
HomeDir Drive: H:
Logon Script: scripts\logon.bat
Profile Path: \\frodo\Profiles\met
Domain: MIDEARTH
Account desc:
Workstations: melbelle
Munged dial:
Logon time: 0
Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT
Password last set: Sat, 14 Dec 2002 14:37:03 GMT
Password can change: Sat, 14 Dec 2002 14:37:03 GMT
Password must change: Mon, 18 Jan 2038 20:14:07 GMT
</pre><p>
</p><p>
<a class="indexterm" name="id2597282"></a>
Accounts can also be listed in the older <code class="literal">smbpasswd</code> format:
</p><pre class="screen">
<code class="prompt">root# </code><strong class="userinput"><code>pdbedit -Lw</code></strong>
root:0:84B0D8E14D158FF8417EAF50CFAC29C3:
AF6DD3FD4E2EA8BDE1695A3F05EFBF52:[U ]:LCT-42681AB8:
jht:1000:6BBC4159020A52741486235A2333E4D2:
CC099521AD554A3C3CF2556274DBCFBC:[U ]:LCT-40D75B5B:
rcg:1002:E95D4331A6F23AF8AAD3B435B51404EE:
BB0F2C39B04CA6100F0E535DF8314B43:[U ]:LCT-40D7C5A3:
afw:1003:1AAFA7F9F6DC1DEAAAD3B435B51404EE:
CE92C2F9471594CDC4E7860CA6BC62DB:[T ]:LCT-40DA501F:
met:1004:A2848CB7E076B435AAD3B435B51404EE:
F25F5D3405085C555236B80B7B22C0D2:[U ]:LCT-4244FAB8:
aurora$:1005:060DE593EA638B8ACC4A19F14D2FF2BB:
060DE593EA638B8ACC4A19F14D2FF2BB:[W ]:LCT-4173E5CC:
temptation$:1006:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
A96703C014E404E33D4049F706C45EE9:[W ]:LCT-42BF0C57:
vaioboss$:1001:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
88A30A095160072784C88F811E89F98A:[W ]:LCT-41C3878D:
frodo$:1008:15891DC6B843ECA41249940C814E316B:
B68EADCCD18E17503D3DAD3E6B0B9A75:[W ]:LCT-42B7979F:
marvel$:1011:BF709959C3C94E0B3958B7B84A3BB6F3:
C610EFE9A385A3E8AA46ADFD576E6881:[W ]:LCT-40F07A4
</pre><p>
<a class="indexterm" name="id2597331"></a>
<a class="indexterm" name="id2597337"></a>
<a class="indexterm" name="id2597344"></a>
<a class="indexterm" name="id2597351"></a>
<a class="indexterm" name="id2597358"></a>
<a class="indexterm" name="id2597365"></a>
The account information that was returned by this command in order from left to right
consists of the following colon separated data:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Login ID.</p></li><li class="listitem"><p>UNIX UID.</p></li><li class="listitem"><p>Microsoft LanManager password hash (password converted to upper-case then hashed.</p></li><li class="listitem"><p>Microsoft NT password hash (hash of the case-preserved password).</p></li><li class="listitem"><p>Samba SAM Account Flags.</p></li><li class="listitem"><p>The LCT data (password last change time).</p></li></ul></div><p>
<a class="indexterm" name="id2597415"></a>
<a class="indexterm" name="id2597422"></a>
The Account Flags parameters are documented in the <code class="literal">pdbedit</code> man page, and are
briefly documented in <a class="link" href="passdb.html#TOSHARG-acctflags" title="Account Flags Management">the Account Flags Management section</a>.
</p><p>
<a class="indexterm" name="id2597449"></a>
The LCT data consists of 8 hexadecimal characters representing the time since January 1, 1970, of
the time when the password was last changed.
</p></div><div class="sect4" title="Adding User Accounts"><div class="titlepage"><div><div><h5 class="title"><a name="id2597460"></a>Adding User Accounts</h5></div></div></div><p>
<a class="indexterm" name="id2597468"></a>
<a class="indexterm" name="id2597475"></a>
<a class="indexterm" name="id2597482"></a>
<a class="indexterm" name="id2597489"></a>
<a class="indexterm" name="id2597496"></a>
The <code class="literal">pdbedit</code> can be used to add a user account to a standalone server
or to a domain. In the example shown here the account for the user <code class="literal">vlaan</code>
has been created before attempting to add the SambaSAMAccount.
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit -a vlaan
new password: secretpw
retype new password: secretpw
Unix username: vlaan
NT username: vlaan
Account Flags: [U ]
User SID: S-1-5-21-726309263-4128913605-1168186429-3014
Primary Group SID: S-1-5-21-726309263-4128913605-1168186429-513
Full Name: Victor Laan
Home Directory: \\frodo\vlaan
HomeDir Drive: H:
Logon Script: scripts\logon.bat
Profile Path: \\frodo\profiles\vlaan
Domain: MIDEARTH
Account desc: Guest User
Workstations:
Munged dial:
Logon time: 0
Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT
Password last set: Wed, 29 Jun 2005 19:35:12 GMT
Password can change: Wed, 29 Jun 2005 19:35:12 GMT
Password must change: Mon, 18 Jan 2038 20:14:07 GMT
Last bad password : 0
Bad password count : 0
Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
</pre><p>
</p></div><div class="sect4" title="Deleting Accounts"><div class="titlepage"><div><div><h5 class="title"><a name="id2597548"></a>Deleting Accounts</h5></div></div></div><p>
<a class="indexterm" name="id2597555"></a>
<a class="indexterm" name="id2597562"></a>
<a class="indexterm" name="id2597569"></a>
<a class="indexterm" name="id2597576"></a>
An account can be deleted from the SambaSAMAccount database
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit -x vlaan
</pre><p>
The account is removed without further screen output. The account is removed only from the
SambaSAMAccount (passdb backend) database, it is not removed from the UNIX account backend.
</p><p>
<a class="indexterm" name="id2597602"></a>
<a class="indexterm" name="id2597609"></a>
The use of the NT4 domain user manager to delete an account will trigger the <em class="parameter"><code>delete user
script</code></em>, but not the <code class="literal">pdbedit</code> tool.
</p></div><div class="sect4" title="Changing User Accounts"><div class="titlepage"><div><div><h5 class="title"><a name="id2597632"></a>Changing User Accounts</h5></div></div></div><p>
<a class="indexterm" name="id2597640"></a>
Refer to the <code class="literal">pdbedit</code> man page for a full synopsis of all operations
that are available with this tool.
</p><p>
<a class="indexterm" name="id2597658"></a>
An example of a simple change in the user account information is the change of the full name
information shown here:
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit -r --fullname="Victor Aluicious Laan" vlaan
...
Primary Group SID: S-1-5-21-726309263-4128913605-1168186429-513
Full Name: Victor Aluicious Laan
Home Directory: \\frodo\vlaan
...
</pre><p>
</p><p>
<a class="indexterm" name="id2597685"></a>
<a class="indexterm" name="id2597692"></a>
<a class="indexterm" name="id2597699"></a>
Let us assume for a moment that a user's password has expired and the user is unable to
change the password at this time. It may be necessary to give the user additional grace time
so that it is possible to continue to work with the account and the original password. This
demonstrates how the password expiration settings may be updated
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit -Lv vlaan
...
Password last set: Sun, 09 Sep 2001 22:21:40 GMT
Password can change: Thu, 03 Jan 2002 15:08:35 GMT
Password must change: Thu, 03 Jan 2002 15:08:35 GMT
Last bad password : Thu, 03 Jan 2002 15:08:35 GMT
Bad password count : 2
...
</pre><p>
<a class="indexterm" name="id2597727"></a>
<a class="indexterm" name="id2597734"></a>
The user has recorded 2 bad logon attempts and the next will lock the account, but the
password is also expired. Here is how this account can be reset:
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit -z vlaan
...
Password last set: Sun, 09 Sep 2001 22:21:40 GMT
Password can change: Thu, 03 Jan 2002 15:08:35 GMT
Password must change: Thu, 03 Jan 2002 15:08:35 GMT
Last bad password : 0
Bad password count : 0
...
</pre><p>
The <code class="literal">Password must change:</code> parameter can be reset like this:
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit --pwd-must-change-time=1200000000 vlaan
...
Password last set: Sun, 09 Sep 2001 22:21:40 GMT
Password can change: Thu, 03 Jan 2002 15:08:35 GMT
Password must change: Thu, 10 Jan 2008 14:20:00 GMT
...
</pre><p>
Another way to use this tools is to set the date like this:
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit --pwd-must-change-time="2010-01-01" \
--time-format="%Y-%m-%d" vlaan
...
Password last set: Sun, 09 Sep 2001 22:21:40 GMT
Password can change: Thu, 03 Jan 2002 15:08:35 GMT
Password must change: Fri, 01 Jan 2010 00:00:00 GMT
...
</pre><p>
<a class="indexterm" name="id2597798"></a>
<a class="indexterm" name="id2597805"></a>
Refer to the strptime man page for specific time format information.
</p><p>
<a class="indexterm" name="id2597816"></a>
<a class="indexterm" name="id2597823"></a>
Please refer to the pdbedit man page for further information relating to SambaSAMAccount
management.
</p><div class="sect5" title="Account Flags Management"><div class="titlepage"><div><div><h6 class="title"><a name="TOSHARG-acctflags"></a>Account Flags Management</h6></div></div></div><p>
<a class="indexterm" name="id2597845"></a>
<a class="indexterm" name="id2597852"></a>
<a class="indexterm" name="id2597861"></a>
<a class="indexterm" name="id2597868"></a>
The Samba SAM account flags are properly called the ACB (account control block) within
the Samba source code. In some parts of the Samba source code they are referred to as the
account encode_bits, and also as the account control flags.
</p><p>
<a class="indexterm" name="id2597883"></a>
<a class="indexterm" name="id2597889"></a>
<a class="indexterm" name="id2597896"></a>
<a class="indexterm" name="id2597903"></a>
<a class="indexterm" name="id2597910"></a>
The manual adjustment of user, machine (workstation or server) or an inter-domain trust
account account flgas should not be necessary under normal conditions of use of Samba. On the other hand,
where this information becomes corrupted for some reason, the ability to correct the damaged data is certainly
useful. The tool of choice by which such correction can be affected is the <code class="literal">pdbedit</code> utility.
</p><p>
<a class="indexterm" name="id2597940"></a>
<a class="indexterm" name="id2597946"></a>
There have been a few requests for information regarding the account flags from developers
who are creating their own Samba management tools. An example of a need for information regarding
the proper management of the account flags is evident when developing scripts that will be used
to manage an LDAP directory.
</p><p>
<a class="indexterm" name="id2597962"></a>
<a class="indexterm" name="id2597969"></a>
The account flag field can contain up to 16 characters. Presently, only 11 are in use.
These are listed in <a class="link" href="passdb.html#accountflags" title="Table 11.2. Samba SAM Account Control Block Flags">Samba SAM Account Control Block Flags</a>.
The order in which the flags are specified to the <code class="literal">pdbedit</code> command is not important.
In fact, they can be set without problem in any order in the SambaAcctFlags record in the LDAP directory.
</p><div class="table"><a name="accountflags"></a><p class="title"><b>Table 11.2. Samba SAM Account Control Block Flags</b></p><div class="table-contents"><table summary="Samba SAM Account Control Block Flags" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Flag</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">D</td><td align="left">Account is disabled.</td></tr><tr><td align="center">H</td><td align="left">A home directory is required.</td></tr><tr><td align="center">I</td><td align="left">An inter-domain trust account.</td></tr><tr><td align="center">L</td><td align="left">Account has been auto-locked.</td></tr><tr><td align="center">M</td><td align="left">An MNS (Microsoft network service) logon account.</td></tr><tr><td align="center">N</td><td align="left">Password not required.</td></tr><tr><td align="center">S</td><td align="left">A server trust account.</td></tr><tr><td align="center">T</td><td align="left">Temporary duplicate account entry.</td></tr><tr><td align="center">U</td><td align="left">A normal user account.</td></tr><tr><td align="center">W</td><td align="left">A workstation trust account.</td></tr><tr><td align="center">X</td><td align="left">Password does not expire.</td></tr></tbody></table></div></div><br class="table-break"><p>
<a class="indexterm" name="id2598200"></a>
<a class="indexterm" name="id2598206"></a>
An example of use of the <code class="literal">pdbedit</code> utility to set the account control flags
is shown here:
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit -r -c "[DLX]" jht
Unix username: jht
NT username: jht
Account Flags: [DHULX ]
User SID: S-1-5-21-729263-4123605-1186429-3000
Primary Group SID: S-1-5-21-729263-4123605-1186429-513
Full Name: John H Terpstra,Utah Office
Home Directory: \\aurora\jht
HomeDir Drive: H:
Logon Script: scripts\logon.bat
Profile Path: \\aurora\profiles\jht
Domain: MIDEARTH
Account desc: BluntObject
Workstations:
Logon time: 0
Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
Kickoff time: 0
Password last set: Sun, 03 Jul 2005 23:19:18 GMT
Password can change: Sun, 03 Jul 2005 23:19:18 GMT
Password must change: Mon, 18 Jan 2038 20:14:07 GMT
Last bad password : 0
Bad password count : 0
Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
</pre><p>
<a class="indexterm" name="id2598262"></a>
The flags can be reset to the default settings by executing:
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit -r -c "[]" jht
Unix username: jht
NT username: jht
Account Flags: [U ]
User SID: S-1-5-21-729263-4123605-1186429-3000
Primary Group SID: S-1-5-21-729263-4123605-1186429-513
Full Name: John H Terpstra,Utah Office
Home Directory: \\aurora\jht
HomeDir Drive: H:
Logon Script: scripts\logon.bat
Profile Path: \\aurora\profiles\jht
Domain: MIDEARTH
Account desc: BluntObject
Workstations:
Logon time: 0
Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
Kickoff time: 0
Password last set: Sun, 03 Jul 2005 23:19:18 GMT
Password can change: Sun, 03 Jul 2005 23:19:18 GMT
Password must change: Mon, 18 Jan 2038 20:14:07 GMT
Last bad password : 0
Bad password count : 0
Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
</pre><p>
</p></div></div><div class="sect4" title="Domain Account Policy Managment"><div class="titlepage"><div><div><h5 class="title"><a name="id2598299"></a>Domain Account Policy Managment</h5></div></div></div><p>
<a class="indexterm" name="id2598307"></a>
<a class="indexterm" name="id2598314"></a>
To view the domain account access policies that may be configured execute:
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit -P ?
No account policy by that name
Account policy names are :
min password length
password history
user must logon to change password
maximum password age
minimum password age
lockout duration
reset count minutes
bad lockout attempt
disconnect time
refuse machine password change
</pre><p>
</p><p>
Commands will be executed to establish controls for our domain as follows:
</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>min password length = 8 characters.</p></li><li class="listitem"><p>password history = last 4 passwords.</p></li><li class="listitem"><p>maximum password age = 90 days.</p></li><li class="listitem"><p>minimum password age = 7 days.</p></li><li class="listitem"><p>bad lockout attempt = 8 bad logon attempts.</p></li><li class="listitem"><p>lockout duration = forever, account must be manually reenabled.</p></li></ol></div><p>
The following command execution will achieve these settings:
</p><pre class="screen">
<code class="prompt">root# </code> pdbedit -P "min password length" -C 8
account policy value for min password length was 5
account policy value for min password length is now 8
<code class="prompt">root# </code> pdbedit -P "password history" -C 4
account policy value for password history was 0
account policy value for password history is now 4
<code class="prompt">root# </code> pdbedit -P "maximum password age" -C 7776000
account policy value for maximum password age was 4294967295
account policy value for maximum password age is now 7776000
<code class="prompt">root# </code> pdbedit -P "minimum password age" -C 604800
account policy value for minimum password age was 0
account policy value for minimum password age is now 7
<code class="prompt">root# </code> pdbedit -P "bad lockout attempt" -C 8
account policy value for bad lockout attempt was 0
account policy value for bad lockout attempt is now 8
<code class="prompt">root# </code> pdbedit -P "lockout duration" -C -1
account policy value for lockout duration was 30
account policy value for lockout duration is now 4294967295
</pre><p>
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
To set the maximum (infinite) lockout time use the value of -1.
</p></div><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p>
Account policies must be set individually on each PDC and BDC. At this time (Samba 3.0.11 to Samba 3.0.14a)
account policies are not replicated automatically. This may be fixed before Samba 3.0.20 ships or some
time there after. Please check the WHATSNEW.txt file in the Samba-3 tarball for specific update notiations
regarding this facility.
</p></div></div></div><div class="sect3" title="Account Import/Export"><div class="titlepage"><div><div><h4 class="title"><a name="id2598461"></a>Account Import/Export</h4></div></div></div><p>
<a class="indexterm" name="id2598469"></a>
<a class="indexterm" name="id2598475"></a>
<a class="indexterm" name="id2598482"></a>
The <code class="literal">pdbedit</code> tool allows import/export of authentication (account)
databases from one backend to another. For example, to import/export accounts from an
old <code class="filename">smbpasswd</code> database to a <em class="parameter"><code>tdbsam</code></em>
backend:
</p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p>
<a class="indexterm" name="id2598519"></a>
</p><pre class="screen">
<code class="prompt">root# </code><strong class="userinput"><code>pdbedit -i smbpasswd -e tdbsam</code></strong>
</pre><p>
</p></li><li class="step" title="Step 2"><p>
<a class="indexterm" name="id2598549"></a>
Replace the <em class="parameter"><code>smbpasswd</code></em> with <em class="parameter"><code>tdbsam</code></em> in the
<em class="parameter"><code>passdb backend</code></em> configuration in <code class="filename">smb.conf</code>.
</p></li></ol></div></div></div></div><div class="sect1" title="Password Backends"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2598586"></a>Password Backends</h2></div></div></div><p>
<a class="indexterm" name="id2598593"></a>
<a class="indexterm" name="id2598600"></a>
Samba offers flexibility in backend account database design. The flexibility is immediately obvious as one
begins to explore this capability. Recent changes to Samba (since 3.0.23) have removed the mulitple backend
feature in order to simplify problems that broke some installations. This removal has made the internal
operation of Samba-3 more consistent and predictable.
</p><p>
<a class="indexterm" name="id2598617"></a>
<a class="indexterm" name="id2598624"></a>
Beginning with Samba 3.0.23 it is no longer possible to specify use of mulitple passdb backends. Earlier
versions of Samba-3 made it possible to specify multiple password backends, and even multiple
backends of the same type. The multiple passdb backend capability caused many problems with name to SID and
SID to name ID resolution. The Samba team wrestled with the challenges and decided that this feature needed
to be removed.
</p><div class="sect2" title="Plaintext"><div class="titlepage"><div><div><h3 class="title"><a name="id2598639"></a>Plaintext</h3></div></div></div><p>
<a class="indexterm" name="id2598647"></a>
<a class="indexterm" name="id2598654"></a>
<a class="indexterm" name="id2598661"></a>
<a class="indexterm" name="id2598668"></a>
<a class="indexterm" name="id2598675"></a>
<a class="indexterm" name="id2598682"></a>
Older versions of Samba retrieved user information from the UNIX user database
and eventually some other fields from the file <code class="filename">/etc/samba/smbpasswd</code>
or <code class="filename">/etc/smbpasswd</code>. When password encryption is disabled, no
SMB-specific data is stored at all. Instead, all operations are conducted via the way
that the Samba host OS will access its <code class="filename">/etc/passwd</code> database.
On most Linux systems, for example, all user and group resolution is done via PAM.
</p></div><div class="sect2" title="smbpasswd: Encrypted Password Database"><div class="titlepage"><div><div><h3 class="title"><a name="id2598715"></a>smbpasswd: Encrypted Password Database</h3></div></div></div><p>
<a class="indexterm" name="id2598723"></a>
<a class="indexterm" name="id2598733"></a>
<a class="indexterm" name="id2598740"></a>
<a class="indexterm" name="id2598747"></a>
Traditionally, when configuring <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = yes</a>
in Samba's <code class="filename">smb.conf</code> file, user account information such as username, LM/NT password hashes,
password change times, and account flags have been stored in the <code class="filename">smbpasswd(5)</code>
file. There are several disadvantages to this approach for sites with large numbers of users
(counted in the thousands).
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
<a class="indexterm" name="id2598789"></a>
The first problem is that all lookups must be performed sequentially. Given that
there are approximately two lookups per domain logon (one during initial logon validation
and one for a session connection setup, such as when mapping a network drive or printer), this
is a performance bottleneck for large sites. What is needed is an indexed approach
such as that used in databases.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2598807"></a>
<a class="indexterm" name="id2598814"></a>
<a class="indexterm" name="id2598821"></a>
<a class="indexterm" name="id2598828"></a>
<a class="indexterm" name="id2598834"></a>
The second problem is that administrators who desire to replicate an smbpasswd file
to more than one Samba server are left to use external tools such as
<code class="literal">rsync(1)</code> and <code class="literal">ssh(1)</code> and write custom,
in-house scripts.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2598860"></a>
<a class="indexterm" name="id2598867"></a>
<a class="indexterm" name="id2598874"></a>
<a class="indexterm" name="id2598880"></a>
<a class="indexterm" name="id2598887"></a>
Finally, the amount of information that is stored in an smbpasswd entry leaves
no room for additional attributes such as a home directory, password expiration time,
or even a relative identifier (RID).
</p></li></ul></div><p>
<a class="indexterm" name="id2598904"></a>
<a class="indexterm" name="id2598911"></a>
<a class="indexterm" name="id2598918"></a>
<a class="indexterm" name="id2598925"></a>
As a result of these deficiencies, a more robust means of storing user attributes
used by smbd was developed. The API that defines access to user accounts
is commonly referred to as the samdb interface (previously, this was called the passdb
API and is still so named in the Samba source code trees).
</p><p>
<a class="indexterm" name="id2598940"></a>
<a class="indexterm" name="id2598947"></a>
<a class="indexterm" name="id2598955"></a>
<a class="indexterm" name="id2598961"></a>
<a class="indexterm" name="id2598968"></a>
Samba provides an enhanced set of passdb backends that overcome the deficiencies
of the smbpasswd plaintext database. These are tdbsam and ldapsam.
Of these, ldapsam will be of most interest to large corporate or enterprise sites.
</p></div><div class="sect2" title="tdbsam"><div class="titlepage"><div><div><h3 class="title"><a name="id2598981"></a>tdbsam</h3></div></div></div><p>
<a class="indexterm" name="id2598989"></a>
<a class="indexterm" name="id2598998"></a>
<a class="indexterm" name="id2599007"></a>
Samba can store user and machine account data in a <span class="quote">“<span class="quote">TDB</span>”</span> (trivial database).
Using this backend does not require any additional configuration. This backend is
recommended for new installations that do not require LDAP.
</p><p>
<a class="indexterm" name="id2599025"></a>
<a class="indexterm" name="id2599031"></a>
<a class="indexterm" name="id2599038"></a>
<a class="indexterm" name="id2599044"></a>
As a general guide, the Samba Team does not recommend using the tdbsam backend for sites
that have 250 or more users. Additionally, tdbsam is not capable of scaling for use
in sites that require PDB/BDC implementations that require replication of the account
database. Clearly, for reason of scalability, the use of ldapsam should be encouraged.
</p><p>
<a class="indexterm" name="id2599061"></a>
<a class="indexterm" name="id2599068"></a>
<a class="indexterm" name="id2599074"></a>
The recommendation of a 250-user limit is purely based on the notion that this
would generally involve a site that has routed networks, possibly spread across
more than one physical location. The Samba Team has not at this time established
the performance-based scalability limits of the tdbsam architecture.
</p><p>
<a class="indexterm" name="id2599090"></a>
<a class="indexterm" name="id2599097"></a>
<a class="indexterm" name="id2599104"></a>
<a class="indexterm" name="id2599111"></a>
There are sites that have thousands of users and yet require only one server.
One site recently reported having 4,500 user accounts on one UNIX system and
reported excellent performance with the <code class="literal">tdbsam</code> passdb backend.
The limitation of where the <code class="literal">tdbsam</code> passdb backend can be used
is not one pertaining to a limitation in the TDB storage system, it is based
only on the need for a reliable distribution mechanism for the SambaSAMAccount
backend.
</p></div><div class="sect2" title="ldapsam"><div class="titlepage"><div><div><h3 class="title"><a name="id2599139"></a>ldapsam</h3></div></div></div><p>
<a class="indexterm" name="id2599147"></a>
<a class="indexterm" name="id2599154"></a>
<a class="indexterm" name="id2599160"></a>
There are a few points to stress that the ldapsam does not provide. The LDAP
support referred to in this documentation does not include:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>A means of retrieving user account information from
a Windows 200x Active Directory server.</p></li><li class="listitem"><p>A means of replacing /etc/passwd.</p></li></ul></div><p>
<a class="indexterm" name="id2599189"></a>
<a class="indexterm" name="id2599196"></a>
<a class="indexterm" name="id2599203"></a>
<a class="indexterm" name="id2599209"></a>
The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be
obtained from <a class="ulink" href="http://www.padl.com/" target="_top">PADL Software</a>. More information about the
configuration of these packages may be found in <a class="ulink" href="http://safari.oreilly.com/?XmlId=1-56592-491-6" target="_top">
<span class="emphasis"><em>LDAP, System Administration</em></span> by Gerald Carter, Chapter 6, Replacing NIS"</a>.
</p><p>
<a class="indexterm" name="id2599240"></a>
<a class="indexterm" name="id2599247"></a>
<a class="indexterm" name="id2599254"></a>
This document describes how to use an LDAP directory for storing Samba user
account information traditionally stored in the smbpasswd(5) file. It is
assumed that the reader already has a basic understanding of LDAP concepts
and has a working directory server already installed. For more information
on LDAP architectures and directories, please refer to the following sites:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><a class="ulink" href="http://www.openldap.org/" target="_top">OpenLDAP</a></p></li><li class="listitem"><p><a class="ulink" href="http://www.sun.com/software/products/directory_srvr_ee/index.xml" target="_top">
Sun One Directory Server</a></p></li><li class="listitem"><p><a class="ulink" href="http://www.novell.com/products/edirectory/" target="_top">Novell eDirectory</a></p></li><li class="listitem"><p><a class="ulink" href="http://www-306.ibm.com/software/tivoli/products/directory-server/" target="_top">IBM
Tivoli Directory Server</a></p></li><li class="listitem"><p><a class="ulink" href="http://www.redhat.com/software/rha/directory/" target="_top">Red Hat Directory
Server</a></p></li><li class="listitem"><p><a class="ulink" href="http://www.linuxsecurity.com/content/view/119229" target="_top">Fedora Directory
Server</a></p></li></ul></div><p>
Two additional Samba resources that may prove to be helpful are:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
<a class="indexterm" name="id2599334"></a>
The <a class="ulink" href="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" target="_top">Samba-PDC-LDAP-HOWTO</a>
maintained by Ignacio Coupeau.
</p></li><li class="listitem"><p>
<a class="indexterm" name="id2599354"></a>
<a class="indexterm" name="id2599360"></a>
<a class="indexterm" name="id2599368"></a>
The NT migration scripts from <a class="ulink" href="http://samba.idealx.org/" target="_top">IDEALX</a> that are
geared to manage users and groups in such a Samba-LDAP domain controller configuration.
Idealx also produced the smbldap-tools and the Interactive Console Management tool.
</p></li></ul></div><div class="sect3" title="Supported LDAP Servers"><div class="titlepage"><div><div><h4 class="title"><a name="id2599387"></a>Supported LDAP Servers</h4></div></div></div><p>
<a class="indexterm" name="id2599395"></a>
<a class="indexterm" name="id2599401"></a>
<a class="indexterm" name="id2599408"></a>
<a class="indexterm" name="id2599415"></a>
The LDAP ldapsam code was developed and tested using the OpenLDAP 2.x server and
client libraries. The same code should work with Netscape's Directory Server and client SDK.
However, there are bound to be compile errors and bugs. These should not be hard to fix.
Please submit fixes via the process outlined in <a class="link" href="bugreport.html" title="Chapter 40. Reporting Bugs">Reporting Bugs</a>.
</p><p>
Samba is capable of working with any standards-compliant LDAP server.
</p></div><div class="sect3" title="Schema and Relationship to the RFC 2307 posixAccount"><div class="titlepage"><div><div><h4 class="title"><a name="id2599442"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div></div><p>
Samba-3.0 includes the necessary schema file for OpenLDAP 2.x in the
<code class="filename">examples/LDAP/samba.schema</code> directory of the source code distribution
tarball. The schema entry for the sambaSamAccount ObjectClass is shown here:
</p><pre class="programlisting">
ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY
DESC 'Samba-3.0 Auxiliary SAM Account'
MUST ( uid $ sambaSID )
MAY ( cn $ sambaLMPassword $ sambaNTPassword $ sambaPwdLastSet $
sambaLogonTime $ sambaLogoffTime $ sambaKickoffTime $
sambaPwdCanChange $ sambaPwdMustChange $ sambaAcctFlags $
displayName $ sambaHomePath $ sambaHomeDrive $ sambaLogonScript $
sambaProfilePath $ description $ sambaUserWorkstations $
sambaPrimaryGroupSID $ sambaDomainName ))
</pre><p>
</p><p>
<a class="indexterm" name="id2599478"></a>
<a class="indexterm" name="id2599485"></a>
<a class="indexterm" name="id2599491"></a>
The <code class="filename">samba.schema</code> file has been formatted for OpenLDAP 2.0/2.1.
The Samba Team owns the OID space used by the above schema and recommends its use.
If you translate the schema to be used with Netscape DS, please submit the modified
schema file as a patch to <a class="ulink" href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>.
</p><p>
<a class="indexterm" name="id2599518"></a>
<a class="indexterm" name="id2599525"></a>
<a class="indexterm" name="id2599532"></a>
<a class="indexterm" name="id2599539"></a>
<a class="indexterm" name="id2599546"></a>
<a class="indexterm" name="id2599552"></a>
<a class="indexterm" name="id2599559"></a>
Just as the smbpasswd file is meant to store information that provides information
additional to a user's <code class="filename">/etc/passwd</code> entry, so is the sambaSamAccount
object meant to supplement the UNIX user account information. A sambaSamAccount is an
<code class="constant">AUXILIARY</code> ObjectClass, so it can be used to augment existing
user account information in the LDAP directory, thus providing information needed
for Samba account handling. However, there are several fields (e.g., uid) that overlap
with the posixAccount ObjectClass outlined in RFC 2307. This is by design.
</p><p>
<a class="indexterm" name="id2599588"></a>
<a class="indexterm" name="id2599595"></a>
<a class="indexterm" name="id2599602"></a>
<a class="indexterm" name="id2599609"></a>
<a class="indexterm" name="id2599616"></a>
<a class="indexterm" name="id2599623"></a>
<a class="indexterm" name="id2599629"></a>
<a class="indexterm" name="id2599636"></a>
<a class="indexterm" name="id2599643"></a>
In order to store all user account information (UNIX and Samba) in the directory,
it is necessary to use the sambaSamAccount and posixAccount ObjectClasses in
combination. However, <code class="literal">smbd</code> will still obtain the user's UNIX account
information via the standard C library calls, such as getpwnam().
This means that the Samba server must also have the LDAP NSS library installed
and functioning correctly. This division of information makes it possible to
store all Samba account information in LDAP, but still maintain UNIX account
information in NIS while the network is transitioning to a full LDAP infrastructure.
</p></div><div class="sect3" title="OpenLDAP Configuration"><div class="titlepage"><div><div><h4 class="title"><a name="id2599668"></a>OpenLDAP Configuration</h4></div></div></div><p>
<a class="indexterm" name="id2599676"></a>
<a class="indexterm" name="id2599683"></a>
<a class="indexterm" name="id2599690"></a>
<a class="indexterm" name="id2599697"></a>
To include support for the sambaSamAccount object in an OpenLDAP directory
server, first copy the samba.schema file to slapd's configuration directory.
The samba.schema file can be found in the directory <code class="filename">examples/LDAP</code>
in the Samba source distribution.
</p><pre class="screen">
<code class="prompt">root# </code><strong class="userinput"><code>cp samba.schema /etc/openldap/schema/</code></strong>
</pre><p>
</p><p>
<a class="indexterm" name="id2599734"></a>
<a class="indexterm" name="id2599740"></a>
<a class="indexterm" name="id2599747"></a>
<a class="indexterm" name="id2599754"></a>
<a class="indexterm" name="id2599761"></a>
<a class="indexterm" name="id2599768"></a>
<a class="indexterm" name="id2599775"></a>
<a class="indexterm" name="id2599782"></a>
Next, include the <code class="filename">samba.schema</code> file in <code class="filename">slapd.conf</code>.
The sambaSamAccount object contains two attributes that depend on other schema
files. The <em class="parameter"><code>uid</code></em> attribute is defined in <code class="filename">cosine.schema</code> and
the <em class="parameter"><code>displayName</code></em> attribute is defined in the <code class="filename">inetorgperson.schema</code>
file. Both of these must be included before the <code class="filename">samba.schema</code> file.
</p><pre class="programlisting">
## /etc/openldap/slapd.conf
## schema files (core.schema is required by default)
include /etc/openldap/schema/core.schema
## needed for sambaSamAccount
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema
include /etc/openldap/schema/samba.schema
....
</pre><p>
</p><p>
<a class="indexterm" name="id2599850"></a>
<a class="indexterm" name="id2599856"></a>
<a class="indexterm" name="id2599863"></a>
<a class="indexterm" name="id2599870"></a>
It is recommended that you maintain some indices on some of the most useful attributes,
as in the following example, to speed up searches made on sambaSamAccount ObjectClasses
(and possibly posixAccount and posixGroup as well):
</p><p>
</p><pre class="programlisting">
# Indices to maintain
## required by OpenLDAP
index objectclass eq
index cn pres,sub,eq
index sn pres,sub,eq
## required to support pdb_getsampwnam
index uid pres,sub,eq
## required to support pdb_getsambapwrid()
index displayName pres,sub,eq
## uncomment these if you are storing posixAccount and
## posixGroup entries in the directory as well
##index uidNumber eq
##index gidNumber eq
##index memberUid eq
index sambaSID eq
index sambaPrimaryGroupSID eq
index sambaDomainName eq
index default sub
</pre><p>
</p><p>
Create the new index by executing:
</p><pre class="screen">
<code class="prompt">root# </code>./sbin/slapindex -f slapd.conf
</pre><p>
</p><p>
Remember to restart slapd after making these changes:
</p><pre class="screen">
<code class="prompt">root# </code><strong class="userinput"><code>/etc/init.d/slapd restart</code></strong>
</pre><p>
</p></div><div class="sect3" title="Initialize the LDAP Database"><div class="titlepage"><div><div><h4 class="title"><a name="id2599940"></a>Initialize the LDAP Database</h4></div></div></div><p>
<a class="indexterm" name="id2599948"></a>
<a class="indexterm" name="id2599955"></a>
<a class="indexterm" name="id2599962"></a>
<a class="indexterm" name="id2599969"></a>
Before you can add accounts to the LDAP database, you must create the account containers
that they will be stored in. The following LDIF file should be modified to match your
needs (DNS entries, and so on):
</p><pre class="programlisting">
# Organization for Samba Base
dn: dc=quenya,dc=org
objectclass: dcObject
objectclass: organization
dc: quenya
o: Quenya Org Network
description: The Samba-3 Network LDAP Example
# Organizational Role for Directory Management
dn: cn=Manager,dc=quenya,dc=org
objectclass: organizationalRole
cn: Manager
description: Directory Manager
# Setting up container for Users OU
dn: ou=People,dc=quenya,dc=org
objectclass: top
objectclass: organizationalUnit
ou: People
# Setting up admin handle for People OU
dn: cn=admin,ou=People,dc=quenya,dc=org
cn: admin
objectclass: top
objectclass: organizationalRole
objectclass: simpleSecurityObject
userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
# Setting up container for groups
dn: ou=Groups,dc=quenya,dc=org
objectclass: top
objectclass: organizationalUnit
ou: Groups
# Setting up admin handle for Groups OU
dn: cn=admin,ou=Groups,dc=quenya,dc=org
cn: admin
objectclass: top
objectclass: organizationalRole
objectclass: simpleSecurityObject
userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
# Setting up container for computers
dn: ou=Computers,dc=quenya,dc=org
objectclass: top
objectclass: organizationalUnit
ou: Computers
# Setting up admin handle for Computers OU
dn: cn=admin,ou=Computers,dc=quenya,dc=org
cn: admin
objectclass: top
objectclass: organizationalRole
objectclass: simpleSecurityObject
userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz
</pre><p>
</p><p>
<a class="indexterm" name="id2600012"></a>
<a class="indexterm" name="id2600018"></a>
The userPassword shown above should be generated using <code class="literal">slappasswd</code>.
</p><p>
<a class="indexterm" name="id2600036"></a>
<a class="indexterm" name="id2600042"></a>
The following command will then load the contents of the LDIF file into the LDAP
database.
<a class="indexterm" name="id2600051"></a>
</p><pre class="screen">
<code class="prompt">$ </code><strong class="userinput"><code>slapadd -v -l initldap.dif</code></strong>
</pre><p>
</p><p>
Do not forget to secure your LDAP server with an adequate access control list
as well as an admin password.
</p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
<a class="indexterm" name="id2600083"></a>
Before Samba can access the LDAP server, you need to store the LDAP admin password
in the Samba-3 <code class="filename">secrets.tdb</code> database by:
<a class="indexterm" name="id2600098"></a>
</p><pre class="screen">
<code class="prompt">root# </code><strong class="userinput"><code>smbpasswd -w <em class="replaceable"><code>secret</code></em></code></strong>
</pre><p>
</p></div></div><div class="sect3" title="Configuring Samba"><div class="titlepage"><div><div><h4 class="title"><a name="id2600125"></a>Configuring Samba</h4></div></div></div><p>
<a class="indexterm" name="id2600133"></a>
<a class="indexterm" name="id2600140"></a>
The following parameters are available in <code class="filename">smb.conf</code> only if your version of Samba was built with
LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found. The
best method to verify that Samba was built with LDAP support is:
</p><pre class="screen">
<code class="prompt">root# </code> smbd -b | grep LDAP
HAVE_LDAP_H
HAVE_LDAP
HAVE_LDAP_DOMAIN2HOSTLIST
HAVE_LDAP_INIT
HAVE_LDAP_INITIALIZE
HAVE_LDAP_SET_REBIND_PROC
HAVE_LIBLDAP
LDAP_SET_REBIND_PROC_ARGS
</pre><p>
If the build of the <code class="literal">smbd</code> command you are using does not produce output
that includes <code class="literal">HAVE_LDAP_H</code> it is necessary to discover why the LDAP headers
and libraries were not found during compilation.
</p><p>LDAP-related smb.conf options include these:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id2600197"></a><em class="parameter"><code>passdb backend = ldapsam:url</code></em></td></tr><tr><td><a class="indexterm" name="id2600209"></a></td></tr><tr><td><a class="indexterm" name="id2600216"></a></td></tr><tr><td><a class="indexterm" name="id2600222"></a></td></tr><tr><td><a class="indexterm" name="id2600229"></a></td></tr><tr><td><a class="indexterm" name="id2600236"></a></td></tr><tr><td><a class="indexterm" name="id2600243"></a></td></tr><tr><td><a class="indexterm" name="id2600250"></a></td></tr><tr><td><a class="indexterm" name="id2600257"></a></td></tr><tr><td><a class="indexterm" name="id2600264"></a></td></tr><tr><td><a class="indexterm" name="id2600271"></a></td></tr><tr><td><a class="indexterm" name="id2600278"></a></td></tr><tr><td><a class="indexterm" name="id2600285"></a></td></tr><tr><td><a class="indexterm" name="id2600292"></a></td></tr></table><p>
</p><p>
These are described in the <code class="filename">smb.conf</code> man page and so are not repeated here. However, an example
for use with an LDAP directory is shown in <a class="link" href="passdb.html#confldapex" title="Example 11.2. Configuration with LDAP">the Configuration with LDAP.</a>
</p><div class="example"><a name="confldapex"></a><p class="title"><b>Example 11.2. Configuration with LDAP</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2600343"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id2600355"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2600366"></a><em class="parameter"><code>netbios name = MORIA</code></em></td></tr><tr><td><a class="indexterm" name="id2600378"></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="id2600415"></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="id2600435"></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="id2600451"></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="id2600467"></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="id2600488"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2600500"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2600512"></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="id2600536"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" title="Accounts and Groups Management"><div class="titlepage"><div><div><h4 class="title"><a name="id2600550"></a>Accounts and Groups Management</h4></div></div></div><p>
<a class="indexterm" name="id2600558"></a>
<a class="indexterm" name="id2600565"></a>
Because user accounts are managed through the sambaSamAccount ObjectClass, you should
modify your existing administration tools to deal with sambaSamAccount attributes.
</p><p>
<a class="indexterm" name="id2600581"></a>
<a class="indexterm" name="id2600588"></a>
<a class="indexterm" name="id2600595"></a>
Machine accounts are managed with the sambaSamAccount ObjectClass, just
like user accounts. However, it is up to you to store those accounts
in a different tree of your LDAP namespace. You should use
<span class="quote">“<span class="quote">ou=Groups,dc=quenya,dc=org</span>”</span> to store groups and
<span class="quote">“<span class="quote">ou=People,dc=quenya,dc=org</span>”</span> to store users. Just configure your
NSS and PAM accordingly (usually, in the <code class="filename">/etc/openldap/sldap.conf</code>
configuration file).
</p><p>
<a class="indexterm" name="id2600624"></a>
<a class="indexterm" name="id2600631"></a>
<a class="indexterm" name="id2600638"></a>
<a class="indexterm" name="id2600645"></a>
In Samba-3, the group management system is based on POSIX
groups. This means that Samba makes use of the posixGroup ObjectClass.
For now, there is no NT-like group system management (global and local
groups). Samba-3 knows only about <code class="constant">Domain Groups</code>
and, unlike MS Windows 2000 and Active Directory, Samba-3 does not
support nested groups.
</p></div><div class="sect3" title="Security and sambaSamAccount"><div class="titlepage"><div><div><h4 class="title"><a name="id2600663"></a>Security and sambaSamAccount</h4></div></div></div><p>
<a class="indexterm" name="id2600671"></a>
There are two important points to remember when discussing the security
of sambaSAMAccount entries in the directory.
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>Never</em></span> retrieve the SambaLMPassword or
<a class="indexterm" name="id2600690"></a>
SambaNTPassword attribute values over an unencrypted LDAP session.</p></li><li class="listitem"><p><span class="emphasis"><em>Never</em></span> allow non-admin users to
view the SambaLMPassword or SambaNTPassword attribute values.</p></li></ul></div><p>
<a class="indexterm" name="id2600711"></a>
<a class="indexterm" name="id2600718"></a>
<a class="indexterm" name="id2600724"></a>
These password hashes are clear-text equivalents and can be used to impersonate
the user without deriving the original clear-text strings. For more information
on the details of LM/NT password hashes, refer to <a class="link" href="passdb.html" title="Chapter 11. Account Information Databases">the
Account Information Database section</a>.
</p><p>
<a class="indexterm" name="id2600746"></a>
<a class="indexterm" name="id2600753"></a>
<a class="indexterm" name="id2600760"></a>
<a class="indexterm" name="id2600766"></a>
To remedy the first security issue, the <a class="link" href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl</a> <code class="filename">smb.conf</code>
parameter defaults to require an encrypted session (<a class="link" href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl = on</a>) using the default port of <code class="constant">636</code> when
contacting the directory server. When using an OpenLDAP server, it
is possible to use the StartTLS LDAP extended operation in the place of LDAPS.
In either case, you are strongly encouraged to use secure communications protocols
(so do not set <a class="link" href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl = off</a>).
</p><p>
<a class="indexterm" name="id2600828"></a>
<a class="indexterm" name="id2600834"></a>
<a class="indexterm" name="id2600841"></a>
Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS
extended operation. However, the OpenLDAP library still provides support for
the older method of securing communication between clients and servers.
</p><p>
<a class="indexterm" name="id2600855"></a>
<a class="indexterm" name="id2600862"></a>
<a class="indexterm" name="id2600869"></a>
The second security precaution is to prevent non-administrative users from
harvesting password hashes from the directory. This can be done using the
following ACL in <code class="filename">slapd.conf</code>:
</p><p>
</p><pre class="programlisting">
## allow the "ldap admin dn" access, but deny everyone else
access to attrs=SambaLMPassword,SambaNTPassword
by dn="cn=Samba Admin,ou=People,dc=quenya,dc=org" write
by * none
</pre><p>
</p></div><div class="sect3" title="LDAP Special Attributes for sambaSamAccounts"><div class="titlepage"><div><div><h4 class="title"><a name="id2600899"></a>LDAP Special Attributes for sambaSamAccounts</h4></div></div></div><p> The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: <a class="link" href="passdb.html#attribobjclPartA" title="Table 11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A">Part A</a>, and <a class="link" href="passdb.html#attribobjclPartB" title="Table 11.4. Attributes in the sambaSamAccount ObjectClass (LDAP), Part B">Part B</a>.
</p><div class="table"><a name="attribobjclPartA"></a><p class="title"><b>Table 11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A</b></p><div class="table-contents"><table summary="Attributes in the sambaSamAccount ObjectClass (LDAP), Part A" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left"><code class="constant">sambaLMPassword</code></td><td align="justify">The LanMan password 16-byte hash stored as a character
representation of a hexadecimal string.</td></tr><tr><td align="left"><code class="constant">sambaNTPassword</code></td><td align="justify">The NT password 16-byte hash stored as a character
representation of a hexadecimal string.</td></tr><tr><td align="left"><code class="constant">sambaPwdLastSet</code></td><td align="justify">The integer time in seconds since 1970 when the
<code class="constant">sambaLMPassword</code> and <code class="constant">sambaNTPassword</code> attributes were last set.
</td></tr><tr><td align="left"><code class="constant">sambaAcctFlags</code></td><td align="justify">String of 11 characters surrounded by square brackets [ ]
representing account flags such as U (user), W (workstation), X (no password expiration),
I (domain trust account), H (home dir required), S (server trust account),
and D (disabled).</td></tr><tr><td align="left"><code class="constant">sambaLogonTime</code></td><td align="justify">Integer value currently unused.</td></tr><tr><td align="left"><code class="constant">sambaLogoffTime</code></td><td align="justify">Integer value currently unused.</td></tr><tr><td align="left"><code class="constant">sambaKickoffTime</code></td><td align="justify">Specifies the time (UNIX time format) when the user
will be locked down and cannot login any longer. If this attribute is omitted, then the account will never expire.
Using this attribute together with shadowExpire of the shadowAccount ObjectClass will enable accounts to
expire completely on an exact date.</td></tr><tr><td align="left"><code class="constant">sambaPwdCanChange</code></td><td align="justify">Specifies the time (UNIX time format)
after which the user is allowed to change his password. If this attribute is not set, the user will be free
to change his password whenever he wants.</td></tr><tr><td align="left"><code class="constant">sambaPwdMustChange</code></td><td align="justify">Specifies the time (UNIX time format) when the user is
forced to change his password. If this value is set to 0, the user will have to change his password at first login.
If this attribute is not set, then the password will never expire.</td></tr><tr><td align="left"><code class="constant">sambaHomeDrive</code></td><td align="justify">Specifies the drive letter to which to map the
UNC path specified by sambaHomePath. The drive letter must be specified in the form <span class="quote">“<span class="quote">X:</span>”</span>
where X is the letter of the drive to map. Refer to the <span class="quote">“<span class="quote">logon drive</span>”</span> parameter in the
smb.conf(5) man page for more information.</td></tr><tr><td align="left"><code class="constant">sambaLogonScript</code></td><td align="justify">The sambaLogonScript property specifies the path of
the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path
is relative to the netlogon share. Refer to the <a class="link" href="smb.conf.5.html#LOGONSCRIPT" target="_top">logon script</a> parameter in the
<code class="filename">smb.conf</code> man page for more information.</td></tr><tr><td align="left"><code class="constant">sambaProfilePath</code></td><td align="justify">Specifies a path to the user's profile.
This value can be a null string, a local absolute path, or a UNC path. Refer to the
<a class="link" href="smb.conf.5.html#LOGONPATH" target="_top">logon path</a> parameter in the <code class="filename">smb.conf</code> man page for more information.</td></tr><tr><td align="left"><code class="constant">sambaHomePath</code></td><td align="justify">The sambaHomePath property specifies the path of
the home directory for the user. The string can be null. If sambaHomeDrive is set and specifies
a drive letter, sambaHomePath should be a UNC path. The path must be a network
UNC path of the form <code class="filename">\\server\share\directory</code>. This value can be a null string.
Refer to the <code class="literal">logon home</code> parameter in the <code class="filename">smb.conf</code> man page for more information.
</td></tr></tbody></table></div></div><br class="table-break"><div class="table"><a name="attribobjclPartB"></a><p class="title"><b>Table 11.4. Attributes in the sambaSamAccount ObjectClass (LDAP), Part B</b></p><div class="table-contents"><table summary="Attributes in the sambaSamAccount ObjectClass (LDAP), Part B" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left"><code class="constant">sambaUserWorkstations</code></td><td align="justify">Here you can give a comma-separated list of machines
on which the user is allowed to login. You may observe problems when you try to connect to a Samba domain member.
Because domain members are not in this list, the domain controllers will reject them. Where this attribute is omitted,
the default implies no restrictions.
</td></tr><tr><td align="left"><code class="constant">sambaSID</code></td><td align="justify">The security identifier(SID) of the user.
The Windows equivalent of UNIX UIDs.</td></tr><tr><td align="left"><code class="constant">sambaPrimaryGroupSID</code></td><td align="justify">The security identifier (SID) of the primary group
of the user.</td></tr><tr><td align="left"><code class="constant">sambaDomainName</code></td><td align="justify">Domain the user is part of.</td></tr></tbody></table></div></div><br class="table-break"><p>
<a class="indexterm" name="id2601247"></a>
<a class="indexterm" name="id2601254"></a>
The majority of these parameters are only used when Samba is acting as a PDC of
a domain (refer to <a class="link" href="samba-pdc.html" title="Chapter 4. Domain Control">Domain Control</a>, for details on
how to configure Samba as a PDC). The following four attributes
are only stored with the sambaSamAccount entry if the values are non-default values:
</p><div class="itemizedlist"><a class="indexterm" name="id2601276"></a><a class="indexterm" name="id2601283"></a><a class="indexterm" name="id2601290"></a><a class="indexterm" name="id2601296"></a><ul class="itemizedlist" type="disc"><li class="listitem"><p>sambaHomePath</p></li><li class="listitem"><p>sambaLogonScript</p></li><li class="listitem"><p>sambaProfilePath</p></li><li class="listitem"><p>sambaHomeDrive</p></li></ul></div><p>
<a class="indexterm" name="id2601325"></a>
<a class="indexterm" name="id2601332"></a>
<a class="indexterm" name="id2601339"></a>
These attributes are only stored with the sambaSamAccount entry if
the values are non-default values. For example, assume MORIA has now been
configured as a PDC and that <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home = \\%L\%u</a> was defined in
its <code class="filename">smb.conf</code> file. When a user named <span class="quote">“<span class="quote">becky</span>”</span> logs on to the domain,
the <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> string is expanded to \\MORIA\becky.
If the smbHome attribute exists in the entry <span class="quote">“<span class="quote">uid=becky,ou=People,dc=samba,dc=org</span>”</span>,
this value is used. However, if this attribute does not exist, then the value
of the <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> parameter is used in its place. Samba
will only write the attribute value to the directory entry if the value is
something other than the default (e.g., <code class="filename">\\MOBY\becky</code>).
</p></div><div class="sect3" title="Example LDIF Entries for a sambaSamAccount"><div class="titlepage"><div><div><h4 class="title"><a name="id2601412"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div></div><p>
The following is a working LDIF that demonstrates the use of the SambaSamAccount ObjectClass:
</p><pre class="programlisting">
dn: uid=guest2, ou=People,dc=quenya,dc=org
sambaLMPassword: 878D8014606CDA29677A44EFA1353FC7
sambaPwdMustChange: 2147483647
sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-513
sambaNTPassword: 552902031BEDE9EFAAD3B435B51404EE
sambaPwdLastSet: 1010179124
sambaLogonTime: 0
objectClass: sambaSamAccount
uid: guest2
sambaKickoffTime: 2147483647
sambaAcctFlags: [UX ]
sambaLogoffTime: 2147483647
sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5006
sambaPwdCanChange: 0
</pre><p>
</p><p>
The following is an LDIF entry for using both the sambaSamAccount and
posixAccount ObjectClasses:
</p><pre class="programlisting">
dn: uid=gcarter, ou=People,dc=quenya,dc=org
sambaLogonTime: 0
displayName: Gerald Carter
sambaLMPassword: 552902031BEDE9EFAAD3B435B51404EE
sambaPrimaryGroupSID: S-1-5-21-2447931902-1787058256-3961074038-1201
objectClass: posixAccount
objectClass: sambaSamAccount
sambaAcctFlags: [UX ]
userPassword: {crypt}BpM2ej8Rkzogo
uid: gcarter
uidNumber: 9000
cn: Gerald Carter
loginShell: /bin/bash
logoffTime: 2147483647
gidNumber: 100
sambaKickoffTime: 2147483647
sambaPwdLastSet: 1010179230
sambaSID: S-1-5-21-2447931902-1787058256-3961074038-5004
homeDirectory: /home/moria/gcarter
sambaPwdCanChange: 0
sambaPwdMustChange: 2147483647
sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7
</pre><p>
</p></div><div class="sect3" title="Password Synchronization"><div class="titlepage"><div><div><h4 class="title"><a name="id2601460"></a>Password Synchronization</h4></div></div></div><p>
Samba-3 and later can update the non-Samba (LDAP) password stored with an account. When
using pam_ldap, this allows changing both UNIX and Windows passwords at once.
</p><p>The <a class="link" href="smb.conf.5.html#LDAPPASSWDSYNC" target="_top">ldap passwd sync</a> options can have the values shown in
<a class="link" href="passdb.html#ldappwsync" title="Table 11.5. Possible ldap passwd sync Values">Possible <span class="emphasis"><em>ldap passwd sync</em></span> Values</a>.</p><div class="table"><a name="ldappwsync"></a><p class="title"><b>Table 11.5. Possible <em class="parameter"><code>ldap passwd sync</code></em> Values</b></p><div class="table-contents"><table summary="Possible ldap passwd sync Values" border="1"><colgroup><col align="left"><col align="justify"></colgroup><thead><tr><th align="left">Value</th><th align="center">Description</th></tr></thead><tbody><tr><td align="left">yes</td><td align="justify"><p>When the user changes his password, update
<code class="constant">SambaNTPassword</code>, <code class="constant">SambaLMPassword</code>,
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
<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
worry about the other fields. This option is only available on some LDAP servers and
only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.</p></td></tr></tbody></table></div></div><br class="table-break"><p>More information can be found in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect3" title="Using OpenLDAP Overlay for Password Synchronization"><div class="titlepage"><div><div><h4 class="title"><a name="id2601612"></a>Using OpenLDAP Overlay for Password Synchronization</h4></div></div></div><p>
Howard Chu has written a special overlay called <code class="literal">smbk5pwd</code>. This tool modifies the
<code class="literal">SambaNTPassword</code>, <code class="literal">SambaLMPassword</code> and <code class="literal">Heimdal</code>
hashes in an OpenLDAP entry when an LDAP_EXOP_X_MODIFY_PASSWD operation is performed.
</p><p>
The overlay is shipped with OpenLDAP-2.3 and can be found in the
<code class="filename">contrib/slapd-modules/smbk5pwd</code> subdirectory. This module can also be used with
OpenLDAP-2.2.
</p></div></div></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2601663"></a>Common Errors</h2></div></div></div><div class="sect2" title="Users Cannot Logon"><div class="titlepage"><div><div><h3 class="title"><a name="id2601669"></a>Users Cannot Logon</h3></div></div></div><p><span class="quote">“<span class="quote">I've installed Samba, but now I can't log on with my UNIX account! </span>”</span></p><p>Make sure your user has been added to the current Samba <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>.
Read the <a class="link" href="passdb.html#acctmgmttools" title="Account Management Tools">Account Management Tools,</a> for details.</p></div><div class="sect2" title="Configuration of auth methods"><div class="titlepage"><div><div><h3 class="title"><a name="id2601707"></a>Configuration of <em class="parameter"><code>auth methods</code></em></h3></div></div></div><p>
When explicitly setting an <a class="link" href="smb.conf.5.html#AUTHMETHODS" target="_top">auth methods</a> parameter,
<em class="parameter"><code>guest</code></em> must be specified as the first entry on the line
for example, <a class="link" href="smb.conf.5.html#AUTHMETHODS" target="_top">auth methods = guest sam</a>.
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="groupmapping.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 10. Network Browsing </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 12. Group Mapping: MS Windows and UNIX</td></tr></table></div></body></html>
|
