8 <firstname>Olivier (lem)</firstname><surname>Lemaire</surname>
10 <orgname>IDEALX</orgname>
11 <address><email>olem@IDEALX.org</email></address>
15 <pubdate>May 24, 2003</pubdate>
17 <title>Account Information Databases</title>
20 Samba-3 implements a new capability to work concurrently with mulitple account backends.
21 The possible new combinations of password backends allows Samba-3 a degree of flexibility
22 and scalability that previously could be achieved only with MS Windows Active Directory.
23 This chapter describes the new functionality and how to get the most out of it.
27 In the course of development of Samba-3 a number of requests were received to provide the
28 ability to migrate MS Windows NT4 SAM accounts to Samba-3 without the need to provide
29 matching Unix/Linux accounts. We called this the <emphasis>Non Unix Accounts (NUA)</emphasis>
30 capability. The intent was that an administrator could decide to use the <emphasis>tdbsam</emphasis>
31 backend and by simply specifying <emphasis>"passdb backedn = tdbsam_nua, guest"</emphasis>
32 this would allow Samba-3 to implement a solution that did not use Unix accounts per se. Late
33 in the development cycle the team doing this work hit upon some obstacles that prevents this
34 solution from being used. Given the delays with Samba-3 release a decision was made to NOT
35 deliver this functionality until a better method of recognising NT Group SIDs from NT User
36 SIDs could be found. This feature may thus return during the life cycle for the Samba-3 series.
40 Samba-3.0.0 does NOT support Non-Unix Account (NUA) operation.
44 <title>Features and Benefits</title>
47 Samba-3 provides for complete backwards compatibility with Samba-2.2.x functionality
52 <title>Backwards Compatibility Backends</title>
53 <varlistentry><term>Plain Text:</term>
56 This option uses nothing but the Unix/Linux <filename>/etc/passwd</filename>
57 style back end. On systems that have PAM (Pluggable Authentication Modules)
58 support all PAM modules are supported. The behaviour is just as it was with
59 Samba-2.2.x, and the protocol limitations imposed by MS Windows clients
65 <varlistentry><term>smbpasswd:</term>
68 This option allows continues use of the <filename>smbpasswd</filename>
69 file that maintains a plain ASCII (text) layout that includes the MS Windows
70 LanMan and NT encrypted passwords as well as a field that stores some
71 account information. This form of password backend does NOT store any of
72 the MS Windows NT/200x SAM (Security Account Manager) information needed to
73 provide the extended controls that are needed for more comprehensive
74 interoperation with MS Windows NT4 / 200x servers.
79 <varlistentry><term>ldapsam_compat (Samba-2.2 LDAP Compatibilty):</term>
82 There is a password backend option that allows continued operation with
83 a existing OpenLDAP backend that uses the Samba-2.2.x LDAP schema extension.
84 This option is provided primarily as a migration tool, although there is
85 no reason to force migration at this time.
92 Samba-3 introduces the following new password backend capabilities:
96 <title>New Backends</title>
97 <varlistentry><term>tdbsam:</term>
100 The <emphasis>tdbsam</emphasis> password backend stores the old <emphasis>
101 smbpasswd</emphasis> information PLUS the extended MS Windows NT / 200x
102 SAM information into a binary format TDB (trivial database) file.
103 The inclusion of the extended information makes it possible for Samba-3
104 to implement the same account and system access controls that are possible
105 with MS Windows NT4 and MS Windows 200x based systems.
109 The inclusion of the <emphasis>tdbssam</emphasis> capability is a direct
110 response to user requests to allow simple site operation without the overhead
111 of the complexities of running OpenLDAP. It is recommended to use this only
112 for sites that have fewer than 250 users. For larger sites or implementations
113 the use of OpenLDAP or of Active Directory integration is strongly recommended.
118 <varlistentry><term>ldapsam:</term>
121 Samba-3 has a new and extended LDAP implementation that requires configuration
122 of OpenLDAP with a new format samba schema. The new format schema file is
123 included in the <filename>~samba/examples/LDAP</filename> directory.
127 The new LDAP implmentation significantly expands the control abilities that
128 were possible with prior versions of Samba. It is not possible to specify
129 "per user" profile settings, home directories, account access controls, and
130 much more. Corporate sites will see that the Samba-Team has listened to their
131 requests both for capability and to allow greater scalability.
136 <varlistentry><term>mysqlsam (MySQL based backend):</term>
139 It is expected that the MySQL based SAM will be very popular in some corners.
140 This database backend will be on considerable interest to sites that want to
141 leverage existing MySQL technology.
146 <varlistentry><term>xmlsam (XML based datafile):</term>
149 Allows the account and password data to be stored in an XML format
150 data file. This backend is NOT recommended for normal operation, it is
151 provided for developmental and for experimental use only. We recognise
152 that this will not stop some people from using it anyhow, it should work
153 but is NOT officially supported at this time (and likely will not be
158 The xmlsam option can be useful for account migration between database
159 backends. Use of this tool will allow the data to be edited before migration
160 into another backend format.
165 <varlistentry><term>nisplussam:</term>
168 The NIS+ based passdb backend. Takes name NIS domain as an
169 optional argument. Only works with Sun NIS+ servers.
174 <varlistentry><term>plugin:</term>
177 This option allows any external non-Samba backend to interface directly
178 to the samba code. This facility will allow third part vendors to provide
179 a proprietary backend to Samba-3.
188 <title>Technical Information</title>
191 Old windows clients send plain text passwords over the wire. Samba can check these
192 passwords by crypting them and comparing them to the hash stored in the unix user database.
196 Newer windows clients send encrypted passwords (so-called Lanman and NT hashes) over
197 the wire, instead of plain text passwords. The newest clients will send only encrypted
198 passwords and refuse to send plain text passwords, unless their registry is tweaked.
202 These passwords can't be converted to unix style encrypted passwords. Because of that
203 you can't use the standard unix user database, and you have to store the Lanman and NT
204 hashes somewhere else.
208 In addition to differently encrypted passwords, windows also stores certain data for each
209 user that is not stored in a unix user database. e.g: workstations the user may logon from,
210 the location where the users' profile is stored, and so on. Samba retrieves and stores this
211 information using a "passdb backend". Commonly available backends are LDAP, plain text
212 file, MySQL and nisplus. For more information, see the man page for &smb.conf; regarding the
213 <command>passdb backend = </command> parameter.
217 <title>Important Notes About Security</title>
220 The unix and SMB password encryption techniques seem similar on the surface. This
221 similarity is, however, only skin deep. The unix scheme typically sends clear text
222 passwords over the network when logging in. This is bad. The SMB encryption scheme
223 never sends the cleartext password over the network but it does store the 16 byte
224 hashed values on disk. This is also bad. Why? Because the 16 byte hashed values
225 are a "password equivalent". You cannot derive the user's password from them, but
226 they could potentially be used in a modified client to gain access to a server.
227 This would require considerable technical knowledge on behalf of the attacker but
228 is perfectly possible. You should thus treat the data stored in whatever passdb
229 backend you use (smbpasswd file, ldap, mysql) as though it contained the cleartext
230 passwords of all your users. Its contents must be kept secret, and the file should
231 be protected accordingly.
235 Ideally we would like a password scheme that involves neither plain text passwords
236 on the net nor on disk. Unfortunately this is not available as Samba is stuck with
237 having to be compatible with other SMB systems (WinNT, WfWg, Win95 etc).
241 Windows NT 4.0 Service pack 3 changed the default setting so that plaintext passwords
242 are disabled from being sent over the wire. This mandates either the use of encrypted
243 password support or edit the Windows NT registry to re-enable plaintext passwords.
247 The following versions of MS Windows do not support full domain security protocols,
248 although they may log onto a domain environment:
253 MS DOS Network client 3.0 with the basic network redirector installed
257 Windows 95 with the network redirector update installed
271 MS Windows XP Home does not have facilities to become a domain member and it can
272 not participate in domain logons.
277 The following versions of MS Windows fully support domain security protocols.
281 <listitem><para>Windows NT 3.5x</para></listitem>
282 <listitem><para>Windows NT 4.0</para></listitem>
283 <listitem><para>Windows 2000 Professional</para></listitem>
284 <listitem><para>Windows 200x Server/Advanced Server</para></listitem>
285 <listitem><para>Windows XP Professional</para></listitem>
289 All current release of Microsoft SMB/CIFS clients support authentication via the
290 SMB Challenge/Response mechanism described here. Enabling clear text authentication
291 does not disable the ability of the client to participate in encrypted authentication.
292 Instead, it allows the client to negotiate either plain text _or_ encrypted password
297 MS Windows clients will cache the encrypted password alone. Where plain text passwords
298 are re-enabled, through the appropriate registry change, the plain text password is NEVER
299 cached. This means that in the event that a network connections should become disconnected
300 (broken) only the cached (encrypted) password will be sent to the resource server to
301 affect a auto-reconnect. If the resource server does not support encrypted passwords the
302 auto-reconnect will fail. <emphasis>USE OF ENCRYPTED PASSWORDS IS STRONGLY ADVISED.</emphasis>
306 <title>Advantages of Encrypted Passwords</title>
309 <listitem><para>Plain text passwords are not passed across
310 the network. Someone using a network sniffer cannot just
311 record passwords going to the SMB server.</para></listitem>
313 <listitem><para>Plain text passwords are not stored anywhere in
314 memory or on disk.</para></listitem>
316 <listitem><para>WinNT doesn't like talking to a server
317 that does not support encrypted passwords. It will refuse
318 to browse the server if the server is also in user level
319 security mode. It will insist on prompting the user for the
320 password on each connection, which is very annoying. The
321 only things you can do to stop this is to use SMB encryption.
324 <listitem><para>Encrypted password support allows automatic share
325 (resource) reconnects.</para></listitem>
327 <listitem><para>Encrypted passwords are essential for PDC/BDC
328 operation.</para></listitem>
334 <title>Advantages of non-encrypted passwords</title>
337 <listitem><para>Plain text passwords are not kept
338 on disk, and are NOT cached in memory. </para></listitem>
340 <listitem><para>Uses same password file as other unix
341 services such as login and ftp</para></listitem>
343 <listitem><para>Use of other services (such as telnet and ftp) which
344 send plain text passwords over the net, so sending them for SMB
345 isn't such a big deal.</para></listitem>
352 <title>Account Management Tools</title>
355 Samba-3 provides two (2) tools for management of User and machine accounts. These tools are
356 called <filename>smbpasswd</filename> and <filename>pdbedit</filename>. A third tool is under
357 development but is NOT expected to ship in time for Samba-3.0.0. The new tool will be a TCL/TK
358 GUI tool that looks much like the MS Windows NT4 Domain User Manager - hopefully this will
359 be announced in time for samba-3.0.1 release timing.
362 <title>The <emphasis>smbpasswd</emphasis> Command</title>
365 The smbpasswd utility is a utility similar to the <command>passwd</command>
366 or <command>yppasswd</command> programs. It maintains the two 32 byte password
367 fields in the passdb backend.
371 <command>smbpasswd</command> works in a client-server mode where it contacts the
372 local smbd to change the user's password on its behalf.This has enormous benefits
377 <command>smbpasswd</command> has the capability to change passwords on Windows NT
378 servers (this only works when the request is sent to the NT Primary Domain Controller
379 if changing an NT Domain user's password).
383 <command>smbpasswd</command> can be used to:
388 <emphasis>add</emphasis> user or machine accounts
392 <emphasis>delete</emphasis> user or machine accounts
396 <emphasis>enable</emphasis> user or machine accounts
400 <emphasis>disable</emphasis> user or machine accounts
404 <emphasis>set to NULL</emphasis> user passwords
408 <emphasis>manage interdomain trust accounts</emphasis>
413 To run smbpasswd as a normal user just type:
418 <prompt>$ </prompt><userinput>smbpasswd</userinput>
419 <prompt>Old SMB password: </prompt><userinput><secret></userinput>
421 For <emphasis>secret</emphasis> type old value here - or hit return if
422 there was no old password
424 <prompt>New SMB Password: </prompt><userinput><new secret></userinput>
425 <prompt>Repeat New SMB Password: </prompt><userinput><new secret></userinput>
430 If the old value does not match the current value stored for that user, or the two
431 new values do not match each other, then the password will not be changed.
435 When invoked by an ordinary user it will only allow change of their own
440 When run by root smbpasswd may take an optional argument, specifying
441 the user name whose SMB password you wish to change. When run as root, smbpasswd
442 does not prompt for or check the old password value, thus allowing root to set passwords
443 for users who have forgotten their passwords.
447 <command>smbpasswd</command> is designed to work in the way familiar to UNIX
448 users who use the <command>passwd</command> or <command>yppasswd</command> commands.
449 While designed for administrative use, this tool provides essential user level
450 password change capabilities.
454 For more details on using <command>smbpasswd</command> refer to the man page (the
455 definitive reference).
460 <title>The <emphasis>pdbedit</emphasis> Command</title>
463 <command>pdbedit</command> is a tool that can be used only by root. It is used to
464 manage the passdb backend. <command>pdbedit</command> can be used to:
469 add, remove or modify user accounts
473 listing user accounts
477 migrate user accounts
482 The <command>pdbedit</command> tool is the only one that can manage the account
483 security and policy settings. It is capable of all operations that smbpasswd can
484 do as well as a super set of them.
488 One particularly important purpose of the <command>pdbedit</command> is to allow
489 the migration of account information from one passdb backend to another. See the
490 <link linkend="XMLpassdb">XML</link> password backend section of this chapter.
494 The following is an example of the user account information that is stored in
495 a tdbsam password backend. This listing was produced by running:
504 User SID: S-1-5-21-1449123459-1407424037-3116680435-2004
505 Primary Group SID: S-1-5-21-1449123459-1407424037-3116680435-1201
506 Full Name: Melissa E Terpstra
507 Home Directory: \\frodo\met\Win9Profile
509 Logon Script: scripts\logon.bat
510 Profile Path: \\frodo\Profiles\met
513 Workstations: melbelle
516 Logoff time: Mon, 18 Jan 2038 20:14:07 GMT
517 Kickoff time: Mon, 18 Jan 2038 20:14:07 GMT
518 Password last set: Sat, 14 Dec 2002 14:37:03 GMT
519 Password can change: Sat, 14 Dec 2002 14:37:03 GMT
520 Password must change: Mon, 18 Jan 2038 20:14:07 GMT
528 <title>Password Backends</title>
531 Samba-3 offers the greatest flexibility in backend account database design of any SMB/CIFS server
532 technology available today. The flexibility is immediately obvious as one begins to explore this
537 It is possible to specify not only multiple different password backends, but even multiple
538 backends of the same type. For example, to use two different tdbsam databases:
543 In smb.conf [globals]
544 passdb backend = tdbsam:/etc/samba/passdb.tdb, \
545 tdbsam:/etc/samba/old-passdb.tdb, guest
551 <title>Plain Text</title>
554 Older versions of samba retrieved user information from the unix user database
555 and eventually some other fields from the file <filename>/etc/samba/smbpasswd</filename>
556 or <filename>/etc/smbpasswd</filename>. When password encryption is disabled, no
557 SMB specific data is stored at all. Instead all operations are conduected via the way
558 that the samba host OS will access it's <filename>/etc/passwd</filename> database.
559 eg: On Linux systems that is done via PAM.
565 <title>smbpasswd - Encrypted Password Database</title>
568 Traditionally, when configuring <ulink url="smb.conf.5.html#ENCRYPTPASSWORDS">"encrypt
569 passwords = yes"</ulink> in Samba's <filename>smb.conf</filename> file, user account
570 information such as username, LM/NT password hashes, password change times, and account
571 flags have been stored in the <filename>smbpasswd(5)</filename> file. There are several
572 disadvantages to this approach for sites with very large numbers of users (counted
578 The first is that all lookups must be performed sequentially. Given that
579 there are approximately two lookups per domain logon (one for a normal
580 session connection such as when mapping a network drive or printer), this
581 is a performance bottleneck for large sites. What is needed is an indexed approach
582 such as is used in databases.
586 The second problem is that administrators who desire to replicate a smbpasswd file
587 to more than one Samba server were left to use external tools such as
588 <command>rsync(1)</command> and <command>ssh(1)</command> and wrote custom,
593 And finally, the amount of information which is stored in an smbpasswd entry leaves
594 no room for additional attributes such as a home directory, password expiration time,
595 or even a Relative Identified (RID).
600 As a result of these defeciencies, a more robust means of storing user attributes
601 used by smbd was developed. The API which defines access to user accounts
602 is commonly referred to as the samdb interface (previously this was called the passdb
603 API, and is still so named in the Samba CVS trees).
607 Samba-3 provides an enhanced set of passdb backends that overcome the deficiencies
608 of the smbpasswd plain text database. These are tdbsam, ldapsam, and xmlsam.
609 Of these ldapsam will be of most interest to large corporate or enterprise sites.
615 <title>tdbsam</title>
617 <para>Samba can store user and machine account data in a "TDB" (Trivial Database).
618 Using this backend doesn't require any additional configuration. This backend is
619 recommended for new installations that do not require LDAP.
623 As a general guide the Samba-Team do NOT recommend using the tdbsam backend for sites
624 that have 250 or more users. Additionally, tdbsam is not capable of scaling for use
625 in sites that require PDB/BDC implmentations that requires replication of the account
626 database. Clearly, for reason of scalability the use of ldapsam should be encouraged.
632 <title>ldapsam</title>
635 There are a few points to stress that the ldapsam does not provide. The LDAP
636 support referred to in the this documentation does not include:
640 <listitem><para>A means of retrieving user account information from
641 an Windows 200x Active Directory server.</para></listitem>
642 <listitem><para>A means of replacing /etc/passwd.</para></listitem>
646 The second item can be accomplished by using LDAP NSS and PAM modules. LGPL
647 versions of these libraries can be obtained from PADL Software
648 (<ulink url="http://www.padl.com/">http://www.padl.com/</ulink>). More
649 information about the configuration of these packages may be found at "LDAP,
650 System Administration; Gerald Carter, O'Reilly; Chapter 6: Replacing NIS".
651 Refer to <ulink url="http://safari.oreilly.com/?XmlId=1-56592-491-6">
652 http://safari.oreilly.com/?XmlId=1-56592-491-6</ulink> for those who might wish to know
653 more about configuration and adminstration of an OpenLDAP server.
657 This document describes how to use an LDAP directory for storing Samba user
658 account information traditionally stored in the smbpasswd(5) file. It is
659 assumed that the reader already has a basic understanding of LDAP concepts
660 and has a working directory server already installed. For more information
661 on LDAP architectures and Directories, please refer to the following sites.
665 <listitem><para>OpenLDAP - <ulink url="http://www.openldap.org/">http://www.openldap.org/</ulink></para></listitem>
666 <listitem><para>iPlanet Directory Server -
667 <ulink url="http://iplanet.netscape.com/directory">http://iplanet.netscape.com/directory</ulink></para></listitem>
671 Two additional Samba resources which may prove to be helpful are
675 <listitem><para>The <ulink url="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html">Samba-PDC-LDAP-HOWTO</ulink>
676 maintained by Ignacio Coupeau.</para></listitem>
678 <listitem><para>The NT migration scripts from <ulink url="http://samba.idealx.org/">IDEALX</ulink> that are
679 geared to manage users and group in such a Samba-LDAP Domain Controller configuration.
684 <title>Supported LDAP Servers</title>
687 The LDAP ldapsam code has been developed and tested using the OpenLDAP 2.0 and 2.1 server and
688 client libraries. The same code should work with Netscape's Directory Server and client SDK.
689 However, there are bound to be compile errors and bugs. These should not be hard to fix.
690 Please submit fixes via <link linkend="bugreport">Bug reporting facility</link>.
696 <title>Schema and Relationship to the RFC 2307 posixAccount</title>
700 Samba 3.0 includes the necessary schema file for OpenLDAP 2.0 in
701 <filename>examples/LDAP/samba.schema</filename>. The sambaAccount objectclass is given here:
706 objectclass ( 1.3.6.1.4.1.7165.2.2.3 NAME 'sambaAccount' SUP top AUXILIARY
707 DESC 'Samba Auxilary Account'
709 MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $
710 logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $
711 displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $
712 description $ userWorkstations $ primaryGroupID $ domain ))
717 The <filename>samba.schema</filename> file has been formatted for OpenLDAP 2.0/2.1.
718 The OID's are owned by the Samba Team and as such is legal to be openly published.
719 If you translate the schema to be used with Netscape DS, please
720 submit the modified schema file as a patch to
721 <ulink url="mailto:jerry@samba.org">jerry@samba.org</ulink>.
725 Just as the smbpasswd file is meant to store information which supplements a
726 user's <filename>/etc/passwd</filename> entry, so is the sambaAccount object
727 meant to supplement the UNIX user account information. A sambaAccount is a
728 <constant>STRUCTURAL</constant> objectclass so it can be stored individually
729 in the directory. However, there are several fields (e.g. uid) which overlap
730 with the posixAccount objectclass outlined in RFC2307. This is by design.
733 <!--olem: we should perhaps have a note about shadowAccounts too as many
734 systems use them, isn'it ? -->
737 In order to store all user account information (UNIX and Samba) in the directory,
738 it is necessary to use the sambaAccount and posixAccount objectclasses in
739 combination. However, smbd will still obtain the user's UNIX account
740 information via the standard C library calls (e.g. getpwnam(), et. al.).
741 This means that the Samba server must also have the LDAP NSS library installed
742 and functioning correctly. This division of information makes it possible to
743 store all Samba account information in LDAP, but still maintain UNIX account
744 information in NIS while the network is transitioning to a full LDAP infrastructure.
749 <title>OpenLDAP configuration</title>
752 To include support for the sambaAccount object in an OpenLDAP directory
753 server, first copy the samba.schema file to slapd's configuration directory.
754 The samba.schema file can be found in the directory <filename>examples/LDAP</filename>
755 in the samba source distribution.
760 <prompt>root# </prompt><userinput>cp samba.schema /etc/openldap/schema/</userinput>
765 Next, include the <filename>samba.schema</filename> file in <filename>slapd.conf</filename>.
766 The sambaAccount object contains two attributes which depend upon other schema
767 files. The 'uid' attribute is defined in <filename>cosine.schema</filename> and
768 the 'displayName' attribute is defined in the <filename>inetorgperson.schema</filename>
769 file. Both of these must be included before the <filename>samba.schema</filename> file.
774 ## /etc/openldap/slapd.conf
776 ## schema files (core.schema is required by default)
777 include /etc/openldap/schema/core.schema
779 ## needed for sambaAccount
780 include /etc/openldap/schema/cosine.schema
781 include /etc/openldap/schema/inetorgperson.schema
782 include /etc/openldap/schema/samba.schema
783 include /etc/openldap/schema/nis.schema
789 It is recommended that you maintain some indices on some of the most usefull attributes,
790 like in the following example, to speed up searches made on sambaAccount objectclasses
791 (and possibly posixAccount and posixGroup as well).
796 # Indices to maintain
797 ## required by OpenLDAP
802 ## required to support pdb_getsampwnam
803 index uid pres,sub,eq
804 ## required to support pdb_getsambapwrid()
805 index displayName pres,sub,eq
807 ## uncomment these if you are storing posixAccount and
808 ## posixGroup entries in the directory as well
815 index sambaPrimaryGroupSID eq
816 index sambaDomainName eq
822 Create the new index by executing:
827 ./sbin/slapindex -f slapd.conf
832 Remember to restart slapd after making these changes:
837 <prompt>root# </prompt><userinput>/etc/init.d/slapd restart</userinput>
844 <title>Configuring Samba</title>
847 The following parameters are available in smb.conf only with <parameter>--with-ldapsam</parameter>
848 was included when compiling Samba. The following parameters are available in smb.conf only if your
849 version of samba was built with LDAP support. Samba automatically builds with LDAP support if the
850 LDAP libraries are found.
854 <listitem><para><ulink url="smb.conf.5.html#PASSDBBACKEND">passdb backend ldapsam:url</ulink></para></listitem>
855 <listitem><para><ulink url="smb.conf.5.html#LDAPSSL">ldap ssl</ulink></para></listitem>
856 <listitem><para><ulink url="smb.conf.5.html#LDAPADMINDN">ldap admin dn</ulink></para></listitem>
857 <listitem><para><ulink url="smb.conf.5.html#LDAPSUFFIX">ldap suffix</ulink></para></listitem>
858 <listitem><para><ulink url="smb.conf.5.html#LDAPFILTER">ldap filter</ulink></para></listitem>
859 <listitem><para><ulink url="smb.conf.5.html#LDAPMACHINSUFFIX">ldap machine suffix</ulink></para></listitem>
860 <listitem><para><ulink url="smb.conf.5.html#LDAPUSERSUFFIX">ldap user suffix</ulink></para></listitem>
861 <listitem><para><ulink url="smb.conf.5.html#LDAPDELETEDN">ldap delete dn</ulink></para></listitem>
862 <listitem><para><ulink url="smb.conf.5.html#LDAPPASSWDSYNC">ldap passwd sync</ulink></para></listitem>
863 <listitem><para><ulink url="smb.conf.5.html#LDAPTRUSTIDS">ldap trust ids</ulink></para></listitem>
868 These are described in the &smb.conf; man
869 page and so will not be repeated here. However, a sample smb.conf file for
870 use with an LDAP directory could appear as
875 ## /usr/local/samba/lib/smb.conf
878 encrypt passwords = yes
880 netbios name = TASHTEGO
883 # ldap related parameters
885 # define the DN to use when binding to the directory servers
886 # The password for this DN is not stored in smb.conf. Rather it
887 # must be set by using 'smbpasswd -w <replaceable>secretpw</replaceable>' to store the
888 # passphrase in the secrets.tdb file. If the "ldap admin dn" values
889 # change, this password will need to be reset.
890 ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org"
892 # Define the SSL option when connecting to the directory
893 # ('off', 'start tls', or 'on' (default))
896 # syntax: passdb backend = ldapsam:ldap://server-name[:port]
897 passdb backend ldapsam:ldap://funball.samba.org
899 # smbpasswd -x delete the entire dn-entry
902 # the machine and user suffix added to the base suffix
903 # wrote WITHOUT quotes. NULL siffixes by default
904 ldap user suffix = ou=People
905 ldap machine suffix = ou=Systems
907 # Trust unix account information in LDAP
908 # (see the smb.conf manpage for details)
911 # specify the base DN to use when searching the directory
912 ldap suffix = "ou=people,dc=samba,dc=org"
914 # generally the default ldap search filter is ok
915 # ldap filter = "(&(uid=%u)(objectclass=sambaAccount))"
922 <title>Accounts and Groups management</title>
925 As users accounts are managed thru the sambaAccount objectclass, you should
926 modify your existing administration tools to deal with sambaAccount attributes.
930 Machines accounts are managed with the sambaAccount objectclass, just
931 like users accounts. However, it's up to you to store thoses accounts
932 in a different tree of you LDAP namespace: you should use
933 "ou=Groups,dc=plainjoe,dc=org" to store groups and
934 "ou=People,dc=plainjoe,dc=org" to store users. Just configure your
935 NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration
940 In Samba release 3.0, the group management system is based on posix
941 groups. This means that Samba makes usage of the posixGroup objectclass.
942 For now, there is no NT-like group system management (global and local
949 <title>Security and sambaAccount</title>
953 There are two important points to remember when discussing the security
954 of sambaAccount entries in the directory.
958 <listitem><para><emphasis>Never</emphasis> retrieve the lmPassword or
959 ntPassword attribute values over an unencrypted LDAP session.</para></listitem>
960 <listitem><para><emphasis>Never</emphasis> allow non-admin users to
961 view the lmPassword or ntPassword attribute values.</para></listitem>
965 These password hashes are clear text equivalents and can be used to impersonate
966 the user without deriving the original clear text strings. For more information
967 on the details of LM/NT password hashes, refer to the
968 <link linkend="passdb">Account Information Database</link> section of this chapter.
972 To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults
973 to require an encrypted session (<command>ldap ssl = on</command>) using
974 the default port of 636
975 when contacting the directory server. When using an OpenLDAP server, it
976 is possible to use the use the StartTLS LDAP extended operation in the place of
977 LDAPS. In either case, you are strongly discouraged to disable this security
978 (<command>ldap ssl = off</command>).
982 Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS
983 extended operation. However, the OpenLDAP library still provides support for
984 the older method of securing communication between clients and servers.
988 The second security precaution is to prevent non-administrative users from
989 harvesting password hashes from the directory. This can be done using the
990 following ACL in <filename>slapd.conf</filename>:
995 ## allow the "ldap admin dn" access, but deny everyone else
996 access to attrs=lmPassword,ntPassword
997 by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write
1005 <title>LDAP special attributes for sambaAccounts</title>
1008 The sambaAccount objectclass is composed of the following attributes:
1012 <listitem><para><constant>lmPassword</constant>: the LANMAN password 16-byte hash stored as a character
1013 representation of a hexidecimal string.</para></listitem>
1015 <listitem><para><constant>ntPassword</constant>: the NT password hash 16-byte stored as a character
1016 representation of a hexidecimal string.</para></listitem>
1018 <listitem><para><constant>pwdLastSet</constant>: The integer time in seconds since 1970 when the
1019 <constant>lmPassword</constant> and <constant>ntPassword</constant> attributes were last set.
1022 <listitem><para><constant>acctFlags</constant>: string of 11 characters surrounded by square brackets []
1023 representing account flags such as U (user), W(workstation), X(no password expiration),
1024 I(Domain trust account), H(Home dir required), S(Server trust account),
1025 and D(disabled).</para></listitem>
1027 <listitem><para><constant>logonTime</constant>: Integer value currently unused</para></listitem>
1029 <listitem><para><constant>logoffTime</constant>: Integer value currently unused</para></listitem>
1031 <listitem><para><constant>kickoffTime</constant>: Integer value currently unused</para></listitem>
1033 <listitem><para><constant>pwdCanChange</constant>: Integer value currently unused</para></listitem>
1035 <listitem><para><constant>pwdMustChange</constant>: Integer value currently unused</para></listitem>
1037 <listitem><para><constant>homeDrive</constant>: specifies the drive letter to which to map the
1038 UNC path specified by homeDirectory. The drive letter must be specified in the form "X:"
1039 where X is the letter of the drive to map. Refer to the "logon drive" parameter in the
1040 smb.conf(5) man page for more information.</para></listitem>
1042 <listitem><para><constant>scriptPath</constant>: The scriptPath property specifies the path of
1043 the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path
1044 is relative to the netlogon share. Refer to the "logon script" parameter in the
1045 smb.conf(5) man page for more information.</para></listitem>
1047 <listitem><para><constant>profilePath</constant>: specifies a path to the user's profile.
1048 This value can be a null string, a local absolute path, or a UNC path. Refer to the
1049 "logon path" parameter in the smb.conf(5) man page for more information.</para></listitem>
1051 <listitem><para><constant>smbHome</constant>: The homeDirectory property specifies the path of
1052 the home directory for the user. The string can be null. If homeDrive is set and specifies
1053 a drive letter, homeDirectory should be a UNC path. The path must be a network
1054 UNC path of the form <filename>\\server\share\directory</filename>. This value can be a null string.
1055 Refer to the <command>logon home</command> parameter in the &smb.conf; man page for more information.
1058 <listitem><para><constant>userWorkstation</constant>: character string value currently unused.
1061 <listitem><para><constant>rid</constant>: the integer representation of the user's relative identifier
1062 (RID).</para></listitem>
1064 <listitem><para><constant>primaryGroupID</constant>: the relative identifier (RID) of the primary group
1065 of the user.</para></listitem>
1067 <listitem><para><constant>domain</constant>: domain the user is part of.</para></listitem>
1071 The majority of these parameters are only used when Samba is acting as a PDC of
1072 a domain (refer to the <link linkend="samba-pdc">Samba as a primary domain controller</link> chapter for details on
1073 how to configure Samba as a Primary Domain Controller). The following four attributes
1074 are only stored with the sambaAccount entry if the values are non-default values:
1078 <listitem><para>smbHome</para></listitem>
1079 <listitem><para>scriptPath</para></listitem>
1080 <listitem><para>logonPath</para></listitem>
1081 <listitem><para>homeDrive</para></listitem>
1085 These attributes are only stored with the sambaAccount entry if
1086 the values are non-default values. For example, assume TASHTEGO has now been
1087 configured as a PDC and that <command>logon home = \\%L\%u</command> was defined in
1088 its <filename>smb.conf</filename> file. When a user named "becky" logons to the domain,
1089 the <parameter>logon home</parameter> string is expanded to \\TASHTEGO\becky.
1090 If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org",
1091 this value is used. However, if this attribute does not exist, then the value
1092 of the <parameter>logon home</parameter> parameter is used in its place. Samba
1093 will only write the attribute value to the directory entry if the value is
1094 something other than the default (e.g. <filename>\\MOBY\becky</filename>).
1100 <title>Example LDIF Entries for a sambaAccount</title>
1103 The following is a working LDIF with the inclusion of the posixAccount objectclass:
1108 dn: uid=guest2, ou=people,dc=plainjoe,dc=org
1109 ntPassword: 878D8014606CDA29677A44EFA1353FC7
1110 pwdMustChange: 2147483647
1111 primaryGroupID: 1201
1112 lmPassword: 552902031BEDE9EFAAD3B435B51404EE
1113 pwdLastSet: 1010179124
1115 objectClass: sambaAccount
1117 kickoffTime: 2147483647
1119 logoffTime: 2147483647
1126 The following is an LDIF entry for using both the sambaAccount and
1127 posixAccount objectclasses:
1132 dn: uid=gcarter, ou=people,dc=plainjoe,dc=org
1134 displayName: Gerald Carter
1135 lmPassword: 552902031BEDE9EFAAD3B435B51404EE
1136 primaryGroupID: 1201
1137 objectClass: posixAccount
1138 objectClass: sambaAccount
1140 userPassword: {crypt}BpM2ej8Rkzogo
1144 loginShell: /bin/bash
1145 logoffTime: 2147483647
1147 kickoffTime: 2147483647
1148 pwdLastSet: 1010179230
1150 homeDirectory: /home/tashtego/gcarter
1152 pwdMustChange: 2147483647
1153 ntPassword: 878D8014606CDA29677A44EFA1353FC7
1160 <title>Password synchronisation</title>
1163 Since version 3.0 samba can update the non-samba (LDAP) password stored with an account. When
1164 using pam_ldap, this allows changing both unix and windows passwords at once.
1167 <para>The <command>ldap passwd sync</command> options can have the following values:</para>
1172 <listitem><para>When the user changes his password, update
1173 <constant>ntPassword</constant>, <constant>lmPassword</constant>
1174 and the <constant>password</constant> fields.</para></listitem>
1179 <listitem><para>Only update <constant>ntPassword</constant> and <constant>lmPassword</constant>.</para></listitem>
1184 <listitem><para>Only update the LDAP password and let the LDAP server worry
1185 about the other fields. This option is only available when
1186 the LDAP library supports LDAP_EXOP_X_MODIFY_PASSWD. </para></listitem>
1190 <para>More information can be found in the <ulink url="smb.conf.5.html#LDAPPASSWDSYNC">smb.conf</ulink> manpage.
1196 <title>ldap trust ids</title>
1199 LDAP Performance can be improved by using the <command>ldap trust ids</command> parameter.
1200 See the <ulink url="smb.conf.5.html#LDAPTRUSTIDS">smb.conf</ulink> manpage for details.
1208 <title>MySQL</title>
1215 <title>Creating the database</title>
1218 You either can set up your own table and specify the field names to pdb_mysql (see below
1219 for the column names) or use the default table. The file <filename>examples/pdb/mysql/mysql.dump</filename>
1220 contains the correct queries to create the required tables. Use the command :
1222 <command>mysql -u<replaceable>username</replaceable> -h<replaceable>hostname</replaceable> -p<replaceable>password</replaceable> <replaceable>databasename</replaceable> > <filename>/path/to/samba/examples/pdb/mysql/mysql.dump</filename></command>
1227 <title>Configuring</title>
1229 <para>This plugin lacks some good documentation, but here is some short info:</para>
1231 <para>Add a the following to the <command>passdb backend</command> variable in your <filename>smb.conf</filename>:
1233 passdb backend = [other-plugins] mysql:identifier [other-plugins]
1237 <para>The identifier can be any string you like, as long as it doesn't collide with
1238 the identifiers of other plugins or other instances of pdb_mysql. If you
1239 specify multiple pdb_mysql.so entries in 'passdb backend', you also need to
1240 use different identifiers!
1244 Additional options can be given thru the &smb.conf; file in the <command>[global]</command> section.
1249 identifier:mysql host - host name, defaults to 'localhost'
1250 identifier:mysql password
1251 identifier:mysql user - defaults to 'samba'
1252 identifier:mysql database - defaults to 'samba'
1253 identifier:mysql port - defaults to 3306
1254 identifier:table - Name of the table containing users
1260 Since the password for the mysql user is stored in the
1261 &smb.conf; file, you should make the the &smb.conf; file
1262 readable only to the user that runs samba. This is considered a security
1263 bug and will be fixed soon.
1267 <para>Names of the columns in this table(I've added column types those columns should have first):</para>
1271 identifier:logon time column - int(9)
1272 identifier:logoff time column - int(9)
1273 identifier:kickoff time column - int(9)
1274 identifier:pass last set time column - int(9)
1275 identifier:pass can change time column - int(9)
1276 identifier:pass must change time column - int(9)
1277 identifier:username column - varchar(255) - unix username
1278 identifier:domain column - varchar(255) - NT domain user is part of
1279 identifier:nt username column - varchar(255) - NT username
1280 identifier:fullname column - varchar(255) - Full name of user
1281 identifier:home dir column - varchar(255) - Unix homedir path
1282 identifier:dir drive column - varchar(2) - Directory drive path (eg: 'H:')
1283 identifier:logon script column - varchar(255)
1284 - Batch file to run on client side when logging on
1285 identifier:profile path column - varchar(255) - Path of profile
1286 identifier:acct desc column - varchar(255) - Some ASCII NT user data
1287 identifier:workstations column - varchar(255)
1288 - Workstations user can logon to (or NULL for all)
1289 identifier:unknown string column - varchar(255) - unknown string
1290 identifier:munged dial column - varchar(255) - ?
1291 identifier:user sid column - varchar(255) - NT user SID
1292 identifier:group sid column - varchar(255) - NT group ID
1293 identifier:lanman pass column - varchar(255) - encrypted lanman password
1294 identifier:nt pass column - varchar(255) - encrypted nt passwd
1295 identifier:plain pass column - varchar(255) - plaintext password
1296 identifier:acct control column - int(9) - nt user data
1297 identifier:unknown 3 column - int(9) - unknown
1298 identifier:logon divs column - int(9) - ?
1299 identifier:hours len column - int(9) - ?
1300 identifier:unknown 5 column - int(9) - unknown
1301 identifier:unknown 6 column - int(9) - unknown
1306 Eventually, you can put a colon (:) after the name of each column, which
1307 should specify the column to update when updating the table. You can also
1308 specify nothing behind the colon - then the data from the field will not be
1315 <title>Using plaintext passwords or encrypted password</title>
1318 I strongly discourage the use of plaintext passwords, however, you can use them:
1322 If you would like to use plaintext passwords, set
1323 'identifier:lanman pass column' and 'identifier:nt pass column' to
1324 'NULL' (without the quotes) and 'identifier:plain pass column' to the
1325 name of the column containing the plaintext passwords.
1329 If you use encrypted passwords, set the 'identifier:plain pass
1330 column' to 'NULL' (without the quotes). This is the default.
1336 <title>Getting non-column data from the table</title>
1339 It is possible to have not all data in the database and making some 'constant'.
1343 For example, you can set 'identifier:fullname column' to :
1344 <command>CONCAT(First_name,' ',Sur_name)</command>
1348 Or, set 'identifier:workstations column' to :
1349 <command>NULL</command></para>
1351 <para>See the MySQL documentation for more language constructs.</para>
1356 <sect2 id="XMLpassdb">
1359 <para>This module requires libxml2 to be installed.</para>
1361 <para>The usage of pdb_xml is pretty straightforward. To export data, use:
1365 <userinput>pdbedit -e xml:filename</userinput>
1369 (where filename is the name of the file to put the data in)
1373 To import data, use:
1374 <userinput>pdbedit -i xml:filename -e current-pdb</userinput>
1378 Where filename is the name to read the data from and current-pdb to put it in.
1382 For example: To migrate (copy) the smbpasswd database into a tdbsam database:
1387 then execute (as root):
1388 pdbedit -i smbpasswd -e tdbsam
1395 <title>Common Errors</title>
1399 - People forget to put their users in their backend and then complain samba
1400 won't authorize them