Copyright 2002 © IDEALX S.A.S. - Contact: samba@IDEALX.org

The Linux Samba-OpenLDAP Howto
(Revision: 1.10 )

Jérôme Tournier
Olivier Lemaire

Revision: 1.10 , generated July 12, 2007

Release:  
Reference:  
Publication date:  
Print date: July 12, 2007
This Howto explains how to set up and use an Linux Departemental Server with Samba an OpenLDAP to replace an existing Microsoft Windows Domain Controler servers and provide central authentication services, file and print sharing for Microsoft Windows and Unix clients.

Table of Contents

1  Introduction

This smbldap-tools aims on helping to use Open Source softwares Linux, Samba and OpenLDAP to replace existing Microsoft Windows Domain Controler servers. It explains how to set up and use a Linux Departemental Server with Samba and OpenLDAP to offer central authentication (Domain Controler), file and print sharing for Microsoft Windows and Unix clients.

1.1  Softwares used

This howto currently runs for:

1.2  Updates of this document

The most up to date release of this document may be found on the smbldap-tools project page available at http://samba.IDEALX.org/.

If you find any bugs in this document, of if you want this document to integrate some additional infos, please drop us a mail with your bug report and/or change request at samba@IDEALX.org.

1.3  Availability of this document

This document is the property of IDEALX (http://www.IDEALX.com/).

Permission is granted to distribute this document under the terms of the GNU Free Documentation License (See http://www.gnu.org/copyleft/fdl.html).



2  Context of this Howto

This Howto aims at helping to configure an Samba + OpenLDAP Primary Domain Controler for Microsoft Windows Workstations (and, using nss_ldap and pam_ldap, a unique source of authentification for all workstations, including Linux and other Unix systems).

For the need of this howto, we took some snakeoils global parameters and default guidelines which are explained hereafter.

2.1  Global parameters

For the need of our example, we settled the following context:

2.2  RedHat base

In this Howto, we took the RedHat/Linux 9 as a base, and made RPM packages for software component involved in this Howto (Samba, OpenLDAP, smbldap-tools, ...) to ease you installing this configuration.

Of course, this do not mean Samba only run on RedHat/Linux nor RedHat/Linux is a better Linux distribution than Debian GNU/Linux. The choice of RedHat/Linux present the advantage to be quickly reproductible by anybody (RedHat Linux is very common on the server market nowadays, and supported by many vendors). However, we presented in section 17 all .spec files used by our packages to help you install and compile the used softwares on your favorite Linux (or any other Operating System in fact).

All available RPM (and SRPM) packages are available on the smbldap-tools project home page at http://samba.IDEALX.org/.

2.3  FHS, LSB and High Availability

Installing and compiling the key softwares (Samba and OpenLDAP), we tried to keep in mind two key principles:
  1. we must enforce File Hierarchy Standard (FHS3) recommandations,
  2. we should follow the Linux Standard Base (LSB4) recommandations
  3. we must think our Primary Domain Controler may be used in a High Available configuration (in a futur revision of this Howto).
Let us know if you think one of these key principles were not correctly enforced: drop a mail to samba@IDEALX.com.



3  Installation

To stick to this Howto5, you must have the following requirements prior to download anything: Additionnaly, you must download and install packages : The smbldap-tools are available on the project page (http://samba.IDEALX.org/dist/); others are part of the Fedora Core release 2 distribution. Only OpenLDAP was downloaded separatly because of the old version available in the distribution.

3.1  OpenLDAP 2.1.29

At the date we wrote this document, release 2.1.29of OpenLDAP was considered stable enough to be used in production environment. We use the release of OpenLDAP provided with Fedora Core release 2. Packages that need to be downloaded are : Once downloaded, install the following packages on your system: 
rpm -Uvh openldap-2.1.29-1.i386.rpm
rpm -Uvh openldap-servers-2.1.29-1.i386.rpm
rpm -Uvh openldap-clients-2.1.29-1.i386.rpm

3.2  Samba 3.0.11rc1

Samba 3.0.11rc1 is the latest release of Samba 3 branch (at the date of this Howto redaction, and used by this Howto). To use Samba with LDAP, ther's no need of compilation options to Samba as LDAP is the default backend used with classic RedHat's Samba packages.

Samba package can be dowloaded on the samba project 7.

Just download the samba packages and install them on your system: 
rpm -Uvh samba-3.0.10-2.i386.rpm
rpm -Uvh samba-client-3.0.10-2.i386.rpm
rpm -Uvh samba-common-3.0.10-2.i386.rpm
Of course, you can also use the default RedHat package.

3.3  smbldap-tools 0.8.8

smbldap-tools is a package containing some useful scripts to manage users/groups when you're using LDAP as source of users/groups datas (for Unix and for Samba). We used those scripts in this Howto to add/delete/modify users and groups.

smbldap-tools are included in the Samba source tree scince release 2.2.5 8, but you will find RPM and SRPMS packages on the smbldap-tools project page.

For this Howto, just download smbldap-tools release 0.8.8 RPM and install it: 
rpm -Uvh smbldap-tools-0.8.8-1.i386.rpm
smbldap-tools will continue to evoluate. Consult the ChangeLog in the CVS source tree to see if changes are interesting for your context. For this Howto setup however, we encourage you to use release 0.8.8 as they are sufficient for the limited use they cover

4  Configuration

4.1  OpenLDAP

You'll need to configure your OpenLDAP server for it to act as a SAM database. Following our context example, we must configure it to : For the needs of this Howto example, we have used the following LDAP DIT: 
(using Relative DN notation)

dc=IDEALX,dc=ORG
 |
 `--- ou=Users     : to store user accounts for Unix and Windows systems
 |
 `--- ou=Computers : to store computer accounts for Windows systems
 |
 `--- ou=Groups    : to store system groups for Unix and Windows 
 |                   systems (or for any other LDAP-aware systems)
 |
 `--- ou=DSA       : to store special accounts (simpleSecurityObject)
                     systems (or for any other LDAP-aware systems)
This DIT is compliant with recommandations from RFC 2307bis. We did not use ou=Host to store computer accounts as there is a difference between TCP/IP hosts and Microsoft Windows computer accounts. We used ou=DSA to store specific security accounts for LDAP Clients, in the context of the smbldap-tools (look at the 5 section for more details and example).

You may choose to use another LDAP tree to store objects: for example, all accounts (shadowAccounts and sambaSAMAccounts) "under" the same DN. We choosed this DIT because of the compliance with RFC 2307bis recommandations, and because we think it's clearer for human comprehension this way.

Using Samba 3.0.11rc1 and OpenLDAP, we will store :

4.1.1  Schemas

The Samba schema must be supported by the OpenLDAP server. To do so, and using the smbldap-tools OpenLDAP RedHat packages, just verify that your /etc/openldap/slapd.conf include the lines like the example hereafter: 
include         /etc/openldap/schema/core.schema
include         /etc/openldap/schema/cosine.schema
include         /etc/openldap/schema/inetorgperson.schema
include         /etc/openldap/schema/nis.schema
include         /etc/openldap/schema/samba.schema

As you can see, we use the inetOrgPerson objectclass because we want to merge organizational with technical data. Doing so will ease administration as a user account will be used to define:
  1. a human user in your company,
  2. a user account for Microsoft Windows and Unix systems,
  3. a user account for any LDAP-aware application.
Doing so is not mandatory: feel free to use a context who feet your needs better if this way is not the one you want to follow.

Note that we use the samba.schema shipped with Samba release 3.0.11rc1 sources.

4.1.2  Server configuration

Configure the slapd server to be a master server on the following suffix: dc=idealx,dc=org. This will result in the following lines in slapd.conf configuration files: 
database   bdb
directory  /var/lib/ldap

suffix     "dc=IDEALX,dc=ORG"
rootdn     "cn=Manager,dc=IDEALX,dc=ORG"

index      objectClass,uidNumber,gidNumber                  eq
index      cn,sn,uid,displayName                            pres,sub,eq
index      memberUid,mail,givenname                 eq,subinitial
index      sambaSID,sambaPrimaryGroupSID,sambaDomainName    eq

Then, position Access Control Lists to protect your datas. This will result in the following lines in the configuration file: 
access to attrs=userPassword,sambaLMPassword,sambaNTPassword
      by self write
      by anonymous auth
      by * none
access to *
      by * read

Finally, define the Root DN password for your server. This will result in the following lines : 
rootpw          mysecretpwd
Don't forget to place mode 600 on file/etc/openldap/slapd.conf to protect your Root DN password, if not already set. You can also set a hashed password in that file: use the slappasswd command. For example, to have the word mysecretpwd hashed with the SSHA algorithm, use the command 
[root@etoile]$ slappasswd -h {SSHA} -s mysecretpwd
{SSHA}X+Qv3lKnVB/oov2uvC6Id1nfEkgYaPrd
Available algorithm are CRYPT, MD5, SMD5, SSHA, and SHA. The default is SSHA. The resulting lines in the file/etc/openldap/slapd.conf will then be 
rootpw      {SSHA}X+Qv3lKnVB/oov2uvC6Id1nfEkgYaPrd

4.1.3  Clients configuration

Configure default settings for LDAP clients by editing /etc/openldap/ldap.conf like in the following example: 
HOST 127.0.0.1
BASE dc=IDEALX,dc=ORG

4.1.4  Start the server

Finally, start your OpenLDAP server using the following 
/etc/init.d/ldap start
Everything should work fine. If not:

4.2  Linux Operating System

You need to tell you Linux box to use LDAP using pam_ldap and nss_ldap. Then, you should run nscd and finish your system LDAP configuration.

4.2.1  pam_ldap, nss_ldap and nscd

Use authconfig 11 to activate pam_ldap : Cache Information mean you're using nscd (man nscd for more info) : if you're going to use pam_ldap and nss_ldap, you should really use it for optimization.

If you don't rely on 'authconfig', you can edit your /etc/pam.d/system-auth by hand, to have something like the following: 
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth        required      /lib/security/pam_env.so
auth        sufficient    /lib/security/pam_unix.so likeauth nullok
auth        sufficient    /lib/security/pam_ldap.so use_first_pass
auth        required      /lib/security/pam_deny.so

account     required      /lib/security/pam_unix.so
account     sufficient    /lib/security/pam_ldap.so

password    required      /lib/security/pam_cracklib.so retry=3 type=
password    sufficient    /lib/security/pam_unix.so nullok use_authtok md5 shadow
password    sufficient    /lib/security/pam_ldap.so use_authtok
password    required      /lib/security/pam_deny.so

session     required      /lib/security/pam_limits.so
session     required      /lib/security/pam_unix.so
session     optional      /lib/security/pam_ldap.so
Warning: a special attention must be taken about the account sufficient parameters as it seems RedHat authconfig tools place it as 'required' in any case (which is not the way you'll need).

4.2.2  /etc/ldap.conf

Edit your /etc/ldap.conf to configure your LDAP parameters: Which should be like the following: 
# Your LDAP server. Must be resolvable without using LDAP.
host 127.0.0.1

# The distinguished name of the search base.
base dc=IDEALX,dc=ORG

# The distinguished name to bind to the server with if the effective user ID 
# is root. Password must be stored in /etc/ldap.secret (mode 600)
rootbinddn cn=nssldap,ou=DSA,dc=IDEALX,dc=ORG

# RFC2307bis naming contexts
nss_base_passwd         ou=Users,dc=IDEALX,dc=ORG?one
nss_base_passwd         ou=Computers,dc=IDEALX,dc=ORG?one
nss_base_shadow         ou=Users,dc=IDEALX,dc=ORG?one
nss_base_group          ou=Groups,dc=IDEALX,dc=ORG?one

# Security options
ssl no
pam_password md5

# - The End

4.2.3  /etc/ldap.secret

You must place in this file, protected by mode 600, the bind password associated with the distinguished name used by nss_ldap to bind to the OpenLDAP directory when the local user is root. In our example, this file must contain the following password: 
nssldapsecretpwd

4.2.4  /etc/nsswitch.conf

Edit your /etc/nswitch.conf to configure your Name Service Switch to use LDAP for users and groups: 
# significative entries for /etc/nsswitch.conf using 
# Samba and OpenLDAP
passwd:     files ldap   
shadow:     files ldap
group:      files ldap

A complete sample /etc/nsswitch.conf is presented in section 17.1.4.

4.3  Samba

Here, we'll configure Samba as a Primary Domain Controler for the Microsoft Windows NT Domain named IDEALX-NT with the SAM database stored in our OpenLDAP server.

4.3.1  Configuration

We need to configure /etc/samba/smb.conf like in the example of 17.1.3, assuming that : Edit your /etc/samba/smb.conf like in the example of 17.1.3 to configure your Samba server. Let make some remarques about this file:

The global section
This section allow you to configure the global parameter of the server. Here takes places all the parameters we defined in the previous paragraph. We also have defined the program used for a user to change his password (passwd program) and the dialog used between the server and the user during the change.

The option "add machine script" allow smbd to add, as root, a new machine account in the doamin. When a machine contact the domain, this script is called and the new machine's account is created in the domain. This makes easily the administration of machine's account. For security reason, the only account allowed to join computer in the domain is the "Administrator" which is a privilege account.

For french users, we added a line that allow smbd to map incoming filenames from a DOS code page. This option is very useful if you want that files and directories in your profiles are saved with all the accents they have. Don't forget to read the man page for more detail: this option is a Western European UNIX character set. The parameter client code page MUST be set to code page 850 in order for the conversion to the UNIX character set to be done correctly.
 
  workgroup = IDEALX-NT
  netbios name = PDC-SRV
  enable privileges = yes
  server string = SAMBA-LDAP PDC Server
  ...
  #unix password sync = Yes
  #passwd program = /usr/local/sbin/smbldap-passwd -u %u
  #passwd chat = "Changing password for*\nNew password*" %n\n "*Retype new password*" %n\n"
  ldap passwd sync = Yes
  ...
  ; SAMBA-LDAP declarations
  passdb backend = ldapsam:ldap://127.0.0.1/
  # ldap filter = (&(objectclass=sambaSamAccount)(uid=%u))
  ldap admin dn = cn=Manager,dc=IDEALX,dc=ORG
  ldap suffix = dc=IDEALX,dc=ORG
  ldap group suffix = ou=Groups
  ldap user suffix = ou=Users
  ldap machine suffix = ou=Computers
  ldap ssl = start_tls

  add machine script = /usr/local/sbin/smbldap-useradd -w "%u"
  add user script = /usr/local/sbin/smbldap-useradd -m "%u"
  ldap delete dn = Yes
  #delete user script = /usr/local/sbin/smbldap-userdel "%u"
  add group script = /usr/local/sbin/smbldap-groupadd -p "%g"
  #delete group script = /usr/local/sbin/smbldap-groupdel "%g"
  add user to group script = /usr/local/sbin/smbldap-groupmod -m "%u" "%g"
  delete user from group script = /usr/local/sbin/smbldap-groupmod -x "%u" "%g"
  set primary group script = /usr/local/sbin/smbldap-usermod -g "%g" "%u"

  ...
  Dos charset = 850
  Unix charset = ISO8859-1

The shares sections
Here takes place all the share sections. In particular, we can define all the user's home directories which are defined by the [homes] section: 
  comment = Home Directories
  valid users = %U
  read only = No
  create mask = 0664
  directory mask = 0775
  browseable = No

Users' profile will be stored in the share named [profiles]. This is the root directory for profiles and the ldap variable sambaProfilePath specify exactly the path for each users. For example if the sambaProfilePath is set to PDC-SRVprofilestestuser, than the profile directory for user testuser is /home/samba/profiles/testuser/. Make sure to have the right permissions for this directory. The sticky bit must be set. Make a simple chmod 1777 /home/samba/profiles and it will be ok. Don't forget that the system doesn't take this change immediately. You should wait several minutes before any profile takes place. 
  path = /home/samba/profiles
  read only = No
  create mask = 0600
  directory mask = 0700
  browseable = No
  guest ok = Yes
  profile acls = Yes
  csc policy = disable
  # next line is a great way to secure the profiles 
  force user = %U
  # next line allows administrator to access all profiles 
  valid users = %U @"Domain Admins"

If you want command's file to be downloaded and ran when a user successfully logged in the windows workstation, you have to define a netlogon section and a netlogon script. The netlogon script must take place in the global section and the script must be a relative path to the [netlogon] service. For example, if the [netlogon] service specifies a path of /home/samba/netlogon (like in our example), then if the script is defined as logon script = STARTUP.BAT, the file that will be downloaded is /home/samba/netlogon/STARTUP.BAT. Finally, we defined a doc section that authorized everybody to browse the /usr/share/doc documentation directory.
 
  ...
  logon script = STARTUP.BAT
  ...

[netlogon]
  path = /home/samba/netlogon/
  browseable = No
  read only = yes

[doc]
  path=/usr/share/doc
  public=yes
  writable=no
  read only=no
  create mask = 0750
  guest ok = Yes

For example, we could have the STARTUP.BAT script that set the documentation directory mounted on the "J" volume on windows clients. Another useful command set windows time synchronized to the server's one: 
NET USE J: \\PDC-SRV\doc
NET TIME \\PDC-SRV /SET /YES

4.3.2  Preparation

You must create some directories, according to your /etc/samba/smb.conf : 
mkdir /home/samba
mkdir /home/samba/netlogon
mkdir /home/samba/profiles
chmod 1777 /home/samba/profiles

4.3.3  Initial entries

Samba must know the passwd of the ldap admin dn (cn=Manager,dc=IDEALX,dc=ORG) user you've specified in smb.conf. This user is used by samba to bind to the directory and must have enough permissions to add/modify accounts stored in the ldap directory.

To do so, use the following command (assuming 'mysecretpwd' is the ldap admin dn password, see your /etc/openldap/slapd.conf configuration file to be sure) : 
[root@pdc-srv samba]# smbpasswd -w mysecretpwd
Setting stored password for "cn=Manager,dc=IDEALX,dc=ORG" in secrets.tdb
Samba will store this datas in /etc/samba/secrets.tbd.

Note that this "ldap admin dn" can be another account than the Root DN : you should use another ldap account who should have permissions to write any sambaSAMAccount and some posixAccount attrs (see section 5 for security considerations).

4.3.4  Testing

To validate your Samba configuration, use testparm who should return 'Loaded services file OK.' without any warnings nor unknow parameter. See man testparm for more info.

4.4  smbldap-tools scripts

Finally, you must configure your smbldap-tools to match your system and LDAP configuration. This can be done in the two files /etc/opt/IDEALX/smbldap-tools/smbldap.conf and /etc/opt/IDEALX/smbldap-tools/smbldap_bind.conf.

4.4.1  Configuration

4.4.2  Initial entries

We need to add some initial entries on the new configured OpenLDAP server:
  1. base entries:
  2. security accounts later used by software clients (Samba and Linux):
The easiest way to set up your directory and add the default base entries can be done using the smbldap-populate script 12: 
[root@etoile root]# smbldap-populate 
Populating LDAP directory for domain IDEALX-NT (S-1-5-21-4205727931-4131263253-1851132061)
(using builtin directory structure)

adding new entry: dc=idealx,dc=org
adding new entry: ou=Users,dc=idealx,dc=org
adding new entry: ou=Groups,dc=idealx,dc=org
adding new entry: ou=Computers,dc=idealx,dc=org
adding new entry: uid=root,ou=Users,dc=idealx,dc=org
adding new entry: uid=nobody,ou=Users,dc=idealx,dc=org
adding new entry: cn=Domain Admins,ou=Groups,dc=idealx,dc=org
adding new entry: cn=Domain Users,ou=Groups,dc=idealx,dc=org
adding new entry: cn=Domain Guests,ou=Groups,dc=idealx,dc=org
adding new entry: cn=Domain Computers,ou=Groups,dc=idealx,dc=org
adding new entry: cn=Administrators,ou=Groups,dc=idealx,dc=org
adding new entry: cn=Account Operators,ou=Groups,dc=idealx,dc=org
adding new entry: cn=Print Operators,ou=Groups,dc=idealx,dc=org
adding new entry: cn=Backup Operators,ou=Groups,dc=idealx,dc=org
adding new entry: cn=Replicators,ou=Groups,dc=idealx,dc=org
adding new entry: sambaDomainName=IDEALX-NT,dc=idealx,dc=org

Please provide a password for the domain root: 
Changing password for root
New password : 
Retype new password :
The sambaDomainName=IDEALX-NT,dc=idealx,dc=org entry define the samba domain and specially it's domain SID. We also use it to defined the next uidNumber and gidNumber available for creating new users and groups. The default values for those numbers are 1000. You can change it with the -u and -g option. For example, if you want the first available value for uidNumber and gidNumber to be set to 1500, you can use the following command : 
smbldap-populate -u 1550 -g 1500
The 'Administrator' user's password, ie the root account password is immediatly defined. In fact, any user placed in the "Domain Admins" group will be granted Windows admin rights for the domain, but only the Administrator account is allowed to join computers to the domain.

Once added, you should add the security accounts for Samba and Linux. To proceed, copy/paste the accounts defined in section 17.3 and add them in the directory with the following command: 
ldapadd -x -h localhost -D "cn=Manager,dc=IDEALX,dc=ORG" -f smbldap-dsa.ldif -W
Finally, set the default password to those accounts: (type your admin DN password, 'mysecretpwd' to complete the command when prompted).

4.5  Test your system

To test your system, we'll create a system account in LDAP (say 'testuser'), and will try login as this new user.

To create a system account in LDAP, use the smbldap-useradd13 script (assuming you have already configured your smbldap-tools): 
[root@pdc-srv tmp]# smbldap-useradd -m testuser1
[root@pdc-srv tmp]# smbldap-passwd testuser1
Changing password for testuser1
New password : 
Retype new password :
Then, try to login on your system (Unix login) as testuser1 (using another console, or using ssh). Everything should work fine : 
[user@host-one:~]$ ssh testuser1@pdc-srv
testuser1@pdc-srv's password:
Last login: Sun Dec 23 15:49:40 2004 from host-one

[testuser1@pdc-srv testuser1]$ id
uid=1000(testuser1) gid=100(users) groupes=100(users)
Dont forget to delete this testuser1 after having completed your tests : 
[root@pdc-srv]# smbldap-userdel -r testuser1

5  Security considerations

5.1  Use an account which is not Root DN

In this HOWTO, we're using the Root DN : the ldap admin dn should be another account than Root DN : you should use another ldap account who should have permissions to write any sambaSAMAccount and some posixAccount attributes.

So if you don't want to use the cn=Manager,dc=idealx,dc=org account anymore, you can use a dedicated account for Samba and another one for the smbldap-tools scripts. The two users were created in section 4.4.2 in the DSA branch : cn=samba,ou=DSA,dc=idealx,dc=org and cn=smbldap-tools,ou=DSA,dc=idealx,dc=org. If the password set for thoses account were respectivly samba and smbldap-tools, you can modify the configuration files as follow (of course, you can use the same account for both samba and smbldap-tools) :

5.2  Secure connections: use TLS !

In this HOWTO, whe are using clear LDAP transport between Samba and OpenLDAP. As both servers implement SSL, you should use TLS transport instead.

If you want to use TLS, you have to create a certificate for each servers. Certificates can be self-signed but it is preferable to have certificates signed by the same authority (CA) if OpenLDAP is configured so that client are requested (TLSVerifyClient demand in slapd.conf file).

The next paragraphs illustrate the few steps needed to set up an example CA and how to create a server's certificate signed by the CA. Refer to the appropriate documentations for more informations (for example http://www.openldap.org/pub/ksoper/OpenLDAP_TLS_howto.html).

You may also want to take a look at IDX-PKI for installing the real thing. See http://www.idealx.com/solutions/idxpki/ for more informations.

Remember one important thing: certificates are created with their common name hardcoded in the certificate. Each time you want to connect to the server in secure mode, you must contact it using this name (and not it's IP address, unless you set it's common name to the IP address)!

Certificates creation
For this example, we'll create a CA authority. Next, we'll create a certificate for the server ldap.idealx.com wich will be signed by the CA.
  1. create the CA key and certificate
  2. create the server key and certificate for ldap.idealx.com server
  3. you then have the three files you need for setting up properly the configuration's server :
Configure the smbldap-tools scripts
The smbldap-tools scripts will connect to the secure directory. We'll then need to create a certificate for this client : use smbldap-tools as common name.
Update the configuration file /etc/opt/IDEALX/smbldap-tools/smbldap.conf :
Configure OpenLDAP
Create a certificate for the OpenLDAP server with common name ldap.idealx.com.
Update the configuration file /etc/openldap/slapd.conf and set : You can also request a valid certificate to all incoming TLS session :
Configure Samba
Simply add one line in the configuration file /etc/samba/smb.conf :
Configure the linux operating system
Check that the /etc/ldap.conf contains the following informations : Be careful to set a proper name for the host directive: it must match the exact name that what given to the OpenLDAP server certificate. It must also be a resolvable name.

5.3  Backup your datas

TODO: how to backup and restore your PDC !

Crucial ! Some scripts may help do the job (even if not used, the will explain what to backup exactly, and how to restore). In fact, those scripts just have to backup: config files (ldap, nss, ldap, samba and tbds..) and the 'SAM' (so a LDIF may do the job). An smbldap-backup and smbldap-restore?

6  Start-Stop servers

To :

7  Migrating posix accounts and groups

Pawel Wielaba has written two scripts smbldap-migrate-unix-accounts and smbldap-migrate-unix-groups to help you migrating users and groups defined in /etc/passwd (and/or /etc/shadow) and /etc/group.

You can find his scripts with the smbldap-tools package (in documentation directory for rpm package). They can also be found on his site : http://www.iem.pw.edu.pl/~wielebap/ldap/smbldap-tools/2/

7.1  users migration (from /etc/shadow)

We suppose that you use the shadow password. We'll then also use the shadow file to migrate password's account. Users migration should be done as follow :
  1. copy /etc/passwd and /etc/shadow in a temporary directory : 
    cp /etc/passwd /etc/shadow /tmp/
  2. remove all accounts on both file that you not want to be in the directory : 
    for user in root nobody bin daemon
do
 export user
 perl -i -pe's@^$ENV{user}:(.*)\n@@' /tmp/passwd
 perl -i -pe's@^$ENV{user}:(.*)\n@@' /tmp/shadow
done
    don't forget to remove the user nobody as it is created when initializing the directory with smbldap-populate.
  3. migrate accounts : 
    /usr/share/doc/smbldap-tools-*/smbldap-migrate-unix-accounts -a -P /tmp/passwd -S /tmp/shadow
  4. remove migrated users from /etc/passwd and /etc/shadow
Note : with the -a option on smbldap-migrate-unix-accounts, the sambaSAMAccount will be added to users. All users having previously a shell defined in /etc/passwd will then be able to connect to the server and update their "windows" password using /opt/IDEALX/sbin/smbldap-passwd script.

7.2  groups migration (from /etc/group)

We'll now migrate all groups defined in /etc/group file. Migration process should be done as follow :
  1. copy /etc/group in a temporary directory : 
    cp /etc/group /tmp/
  2. remove all groups that you not want to be in the directory : 
    for group in root bin daemon
do
        export group
        perl -i -pe's@^$ENV{group}:(.*)\n@@' /tmp/group
done
  3. migrate groups : 
    /usr/share/doc/smbldap-tools-*/smbldap-migrate-unix-groups -a -G /tmp/group
  4. remove migrated groups from /etc/group
Note : with the -a option on smbldap-migrate-unix-groups, the sambaGroupMapping will be added to groups so that they can be used as "windows" groups (samba will than mapped unix groups to windows groups). You should remove this option if you don't want this.



8  Exploitation

8.1  User management

To manager user accounts, you can use:
  1. smbldap-tools, using the following scripts:
  2. idxldapaccounts (webmin module) if you are looking for a nice Graphical User Interface.
  3. Microsoft Windows NT Domain management tools
The first method will be presented hereafter.

8.1.1  A LDAP view

First, let's have a look on what is really a user accounts for LDAP. In fact, there is two kinds of user accounts : Here's a LDAP view of an Unix Account (posixAccount in fact, for this HOWTO) : 
dn: uid=testuser1,ou=Users,dc=IDEALX,dc=ORG
objectClass: top
objectClass: account
objectClass: posixAccount
cn: testuser1
uid: testuser1
uidNumber: 1000
gidNumber: 100
homeDirectory: /home/testuser1
loginShell: /bin/bash
gecos: User
description: User
userPassword: {SSHA}ZSPozTWYsy3addr9yRbqx8q5K+J24pKz

Here's a LDAP view of a Samba user account (sambaSAMAccount) : 
dn: uid=testsmbusers2,ou=Users,dc=idealx,dc=org
objectClass: top,inetOrgPerson,posixAccount,shadowAccount,sambaSAMAccount
cn: testsmbusers2
sn: testsmbusers2
uid: testsmbusers2
uidNumber: 1000
gidNumber: 513
homeDirectory: /home/testsmbusers2
loginShell: /bin/bash
gecos: System User
description: System User
sambaLogonTime: 0
sambaLogoffTime: 2147483647
sambaKickoffTime: 2147483647
sambaPwdCanChange: 0
displayName: System User
sambaSID: S-1-5-21-4231626423-2410014848-2360679739-3000
sambaPrimaryGroupSID: S-1-5-21-4231626423-2410014848-2360679739-513
sambaLogonScript: testsmbusers2.cmd
sambaProfilePath: \\PDC-SRV\profiles\testsmbusers2
sambaHomePath: \\PDC-SRV\home\testsmbusers2
sambaHomeDrive: H:
sambaLMPassword: 7584248B8D2C9F9EAAD3B435B51404EE
sambaAcctFlags: [U]
sambaNTPassword: 186CB09181E2C2ECAAC768C47C729904
sambaPwdLastSet: 1081281346
sambaPwdMustChange: 1085169346
userPassword: {SSHA}jg1v0WaeBkymhWasjeiprxzHxdmTAHd+

Here follow a quick explanation about the attributes used:
Attribute from schema Usage
cn core usually, the username
uid core username
description core TODO
userPassword core password for Unix systems using NSS/PAM LDAP
displayName inetorgperson TODO
uidNumber nis the numeric user number (Unix and Samba)
gidNumber nis the primary group number of the user (Unix)
loginShell nis the logon shell used on Unix systems
gecos nis the long form of the username
homeDirectory nis home directory path for Unix systems
sambaPwdLastSet samba The integer time in seconds since 1970 when
    the lm and ntpasswd were last set.
sambaLogonTime samba timestamp of last logon
sambaLogoffTime samba timestamp of last logoff
sambaKickoffTime samba timestamp of when the user will be logged off automatically
sambaPwdCanChange samba timestamp of when the user is allowed to update the password
sambaPwdMustChange samba timestamp of when the password will expire
sambaPwdLastSet samba timestamp of the last password update
sambaAcctFlags samba specify the type of the samba account
sambaBadPasswordCount samba Bad password attempt count
sambaBadPasswordTime samba Time of the last bad password attempt
    (W=workstation, U=user, D=disabled,
    X=no password expiration,...)
sambaSID samba the secure identifier (SID) of the user
sambaPrimaryGroupID samba the relative identifier (SID) of the primary group
    of the user
sambaHomePath samba specifies the path of the home directory for the
    user. The string can be null. If homeDrive is set and
    specifies a drive letter, homeDirectory should be a
    UNC path. The path must be a network UNC path.
    This value can be a null string
sambaLogonScript samba The scriptPath 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
sambaLMmPassword samba the LANMAN password
sambaNTPassword samba the NT password (md4 hash)
sambaHomeDrive samba specifies the drive letter to which to map the UNC
    path specified by homeDirectory. The drive letter
    must be specified in the form "driveletter:" where
    driveletter is the letter of the drive to map.
    For example: "Z:"
sambaProfilePath samba specifies a path to the user's profile. This value
    can be a null string, a local absolute path, or
    a UNC path

Table 1: Attributes used for a user Account

8.1.2  Using the smbldap-tools scripts

To manipulate user accounts, we've developped a collection of PERL scripts named smbldap-tools : they provide all the tools you need to manage user and groups accounts, in a LDAP directory.

Because we've merged posixAccount, shadowAccount and sambaAccount, those scripts may be used to manage Unix and Windows (Samba) accounts. As most of existing software are LDAP aware, you can use your SAMBA-LDAP PDC to be an unique source of authentification, and the smbldap-tools may offer you a good base to manage user accounts datas.

In this Howto, we have used the following tools to manage user accounts : For a detail used of those scripts, consult the smbldap-tools's documentation on the project homepage14.

Create a Unix (Posix) user account
To create a new posixAccount (only usefull for Unix) named testposixuser (we'll use 'coucou' as the password when asked): 
[root@pdc-srv testsmbuser2]# smbldap-useradd -m testposixuser
[root@pdc-srv testsmbuser2]# smbldap-passwd testposixuser
Changing password for testposixuser
New password for user testposixuser: 
Retype new password for user testposixuser:
Create an Samba user account
To create a new sambaSAMAccount (for use under Unix and Samba) named jdoo (we'll use 'coucou' as the password when asked) : 
[root@pdc-srv testsmbuser2]# smbldap-useradd -a -m -c "John Doo" jdoo
[root@pdc-srv testsmbuser2]# smbldap-passwd jdoo
Changing password for jdoo
New password for user jdoo: 
Retype new password for user jdoo:
Setup an user password
You can use smbldap-passwd as a replacement for the system command passwd and the Samba command smbpasswd: 
[root@pdc-srv testsmbuser2]# smbldap-passwd jdoo
Changing password for jdoo
New password for user jdoo: 
Retype new password for user jdoo:
Delete a Posix user account
Just use the following smbldap-tools command: 
[root@pdc-srv testsmbuser2]# smbldap-userdel -r jdoo
In this example, we wanted to remove the user named 'jdoo' and his home directory.

Delete a Samba user account
Exactly like for the deletion of an Unix account, just use smbldap-userdel.

Modify an user account
Use the smbldap-usermod to modify a user's account. Options available with the smbldap-useradd script are also available here.
Another script smbldap-userinfo can be used by users so that they can update their own informations (such as telephoneNumber, rootNumber, shell, ...) themselves. Note that this implies that correct ACL must be defined on the directory configuration.

8.1.3  Using Idealx Management Console (IMC)

Have a look on the project site (http://www.idealx.org/prj/imc/) for more informations on installation procedure.

8.1.4  Using idxldapaccounts webmin module

If you prefer nice GUI to shell, you should have a look on the idxldapaccounts Webmin module. See http://webmin.idealx.org/. This module is available for both samba2 and samba3. Note that idxldapaccounts is not maintained anymore !

8.1.5  Using the Microsoft Windows NT Domain management tools

You can manager users account using the Microsoft Windows NT Domain management tools. This can be launch using the usrmgr.exe command in a msdos console

8.2  Group management

A unix group need to be mapped to a windows group if you want it to be seen and used from Microsoft Windows environment. This can be done automatically.

To manager group accounts, you can use:
  1. smbldap-tools using the following scripts:
  2. idxldapaccounts if you are looking for a nice Graphical User Interface.
  3. Microsoft Windows NT Domain management tools
The first method will be presented hereafter.

8.2.1  A LDAP view

First, let's have a look on what is really a posix group account for LDAP. Here's a LDAP view of a group named unixGroup: 
dn: cn=unixGroup,ou=Groups,dc=idealx,dc=org
objectClass: posixGroup
cn: unixGroup
gidNumber: 1000
memberUid: usertest1
memberUid: usertest2
Here's a LDAP view of a Samba group named sambaGroup: 
dn: cn=sambaGroup,ou=Groups,dc=idealx,dc=org
objectClass: posixGroup,sambaGroupMapping
gidNumber: 512
cn: sambaGroup
description: Samba Group
sambaSID: S-1-5-21-4231626423-2410014848-2360679739-3001
sambaGroupType: 2
displayName: sambaGroup
memberUid: testsmbuser2
memberUid: testsmbuser1

8.2.2  Windows specials groups

The Windows world come with some built-ins users groups :
Group name rid Group SID Description
Domain Admins 512 $SID-512  
Domain Users 513 $SID-513  
Domain Guests 514 $SID-514  
Print Operators 550 S-1-5-32-550  
Backup Operators 551 S-1-5-32-551  
Replicator 552 S-1-5-32-552  

Table 2: Well known rid and corresponding SID of windows administrative groups. $SID refer to the domain secure ID

8.2.3  Using the smbldap-tools scripts

To manipulate groups, we've developped a collection of PERL scripts named smbldap-tools : they provide all the tools you need to manage user and groups accounts, in a LDAP directory.

Because Samba use posixGroup, those scripts may be used to manage Unix and Windows (Samba) accounts. As most of existing software are LDAP aware, you can use your SAMBA-LDAP PDC to be an unique source of authentification, and the smbldap-tools may offer you a good base to manage user accounts datas.

In this Howto, we have used the following tools to manage groups : For a detail used of those scripts, consult the smbldap-tools's documentation on the project homepage15.

8.2.4  Using Idealx Management Console (IMC)

Have a look on the project site (http://www.idealx.org/prj/imc/) for more informations on installation procedure.

8.2.5  Using idxldapaccounts webmin module

If you prefer nice GUI to shell, you should have a look on the idxldapaccounts Webmin module. See http://webmin.idealx.org/. Note that idxldapaccounts is not maintained anymore !

8.2.6  Using the Microsoft Windows NT Domain management tools

You can manager users account using the Microsoft Windows NT Domain management tools. This can be launch using the usrmgr.exe command in a msdos console

8.3  Computer management

To manage computer accounts, we'll use the following scripts (from smbldap-tools) : Computer accounts are sambaSAMAccounts objects, just like Samba user accounts are.

8.3.1  A LDAP view

Here's a LDAP view of a Samba computer account : 
dn: uid=testhost3$,ou=Computers,dc=IDEALX,dc=ORG
objectClass: top
objectClass: posixAccount
objectClass: sambaSAMAccount
cn: testhost3$
gidNumber: 553
homeDirectory: /dev/null
loginShell: /bin/false
uid: testhost3$
uidNumber: 1005
sambaPwdLastSet: 0
sambaLogonTime: 0
sambaLogoffTime: 2147483647
sambaKickoffTime: 2147483647
sambaPwdCanChange: 0
sambaPwdMustChange: 2147483647
description: Computer Account
rid: 0
primaryGroupID: 0
lmPassword: 7582BF7F733351347D485E46C8E6306E
ntPassword: 7582BF7F733351347D485E46C8E6306E
acctFlags: [W          ]

TODO: explain the LDIF, present attribute types (from schema) and explain them.

8.3.2  Using the smbldap-tools scripts

To manipulate computer accounts, we've developped a collection of PERL scripts named smbldap-tools: they provide all the tools you need to manage user and groups accounts, in a LDAP directory.

In this Howto, we have used the following tools to manage user accounts :
Create a Computer account
To create a computer account, you can use smbldap-tools to manually add accounts : 
[root@pdc-srv root]# smbldap-useradd -w testcomputer1
You can also use the automatic procedure within your Microsoft Windows client (see your client chapter: Microsoft Windows NT, w2k...) for more information.

Delete a Computer account
To delete a computer account, just use smbldap-tools : 
[root@pdc-srv root]# smbldap-userdel testcomputer1$
Instead of removing the computer account, you may want to de-activate the Samba Account. The easyest way is to use the smbldap-usermod script as follow : You can also use an LDAP browser and modify the 'acctFlags' from [W ] to [WD ] ('D' indicating 'Disabled'). To re-activate the computer account, just modifiy [WD ] to [W ]. Sometimes, de/re-activation is a better mean to temporary disable the workstation for some times.

8.4  Profile management

WARNING : Under writing !

TODO: Howto manage profiles (NT profiles, as Unix do the job since... AT&T time...)

8.4.1  Roaming/Roving profiles

When a Microsoft Windows NT user joined the IDEALX-NT domain, his profile is stored in the directory defined in the profile section of the samba configuration file. He has to log out for the profile to be saved. This is a roaming profile : he can use this profile from any computer he want. If his personal configuration changed, it will be integrated in his roaming profile.

In this Howto, we used roaming profiles: the LDAP sambaProfilePath attribute indicate to Samba where to look for those roaming profile (

PDC-SRV
profiles
testsmbuser2 for example), and the [profiles] section of the /etc/samba/smb.conf indicate to samba how to deal with those profiles.

Keep in mind that a 'regular' roaming profile is about 186 Kb of data (even more if users uses big GIF or BMP image as background picture ...): don't forget impact on load/traffic...

8.4.2  Mandatory profiles

The mandatory profile is created by the same way of the roaming profile. The difference is that his profile is made read only by the administrator so that the user can have only one fixed profile on the domain.

To do so, rename the file NTuser.dat to NTuser.man (for MANdatory profile), and remove the right access bit. For our testsmbuser1 user, you'll have to do: 
mv /opt/samba/profiles/testsmbuser1/NTUSER.DAT /opt/samba/profiles/testsmbuser1/NTUSER.MAN
chmod -w /opt/samba/profiles/testsmbuser1/NTUSER.MAN
This way, you may want to set up a common user profile for every user on the Domain.

8.4.3  Logon Scripts

To use Logon Scripts (.BAT or .CMD), just specify the relative path from the netlogon share to the command script desired in the sambaScriptPath attribute for the user.

Variable substitutions (the logon script smb.conf directive when you're using LDAP.

8.4.4  LDAP or not LDAP?

Perhaps, you'll want to use an alternative system policy concerning profiles : granting some user the roaming profile privilege across the domain, while some other may have only roaming profile on one PDC server, and some other won't use roaming profile at all. This alternative way is possible thanks to Samba who will search in the LDAP sambaSAMAccount for the profile location if no information is given by the 'logon drive', 'logon script' and 'logon path' directives of smb.conf.

We'll discuss this alternative in a future revision of this document.

9  Interdomain Trust Relationships

We'll have a look on how making interdomain trust relationships so that Domain properties for each domain are :

9.1  Samba-3 trusts NT4

On the Windows NT Server, open "User Manager", "Policies" menu, and "Trust Relationship". Now create an account for the samba-3 domain : 
domaine: IDEALX-NT
mot de passe: secret
Let's establish the trust from the Samba-3 server : 
net rpc trustdom establish NT4
Note that this command may fail with major release of samba with the following error message: 
[root@etoile root]# net rpc trustdom establish IDEALX
Password:
Could not connect to server POMEROL
[2005/06/23 16:52:36, 0] rpc_parse/parse_prs.c:prs_mem_get(537)
  prs_mem_get: reading data of size 4 would overrun buffer.
[2005/06/23 16:52:36, 0] utils/net_rpc.c:rpc_trustdom_establish(4686)
  WksQueryInfo call failed.
This is caused by the security restrictanonymous parameter set on the Windows NT4 server : 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA\RestrictAnonymous
If so, set it to 0 and restart the NT4 server.

9.2  NT4 trusts Samba-3

On the Samba-3 domain controler, create an account for the NT4 domain : 
smbldap-useradd -i NT4
The created account will have a '$' caracter appended to its name (as workstation account), the sambaSAMAccount objectclass and the 'I' flag. A password will also be asked for this account.

Let's establish the trust from Windows NT Server : open the "User Manager", "Policies" menu, and "Trust Relationship". Now join the trusting domain : enter IDEALX-NT and the password defined in the previous command.



10  Integration

10.1  Fake user root

To allow workstations to be joined to the domain, a root user must exist and used (uid=0).

Such a user is created when initializing the directory whith the smbldap-populate script.

From Samba 3.0.12, it is now possible for admin users to join computers to the domain without using the "root" account. For example, to allow members of the "Domain Admins" group to join computers to the domain, you need to In fact, the 'root' account is needed in the first place so that the SeXXX privileges can be set.

10.2  Workstations integration

10.2.1  Adding a new computer in the domain by creating an account manually

If you want the computer named "testmachine" to be added to the domain IDEALX-NT, you must create a account for it. This can be manually done using the script smbldap-useradd previously described in the section 8.1. Then you can add the computer in the domain, following this steps :

for Microsoft Windows NT 4 (SP1, SP6): for Microsoft Windows NT, Windows XP and Microsoft Windows 2000 :

10.2.2  Adding a new computer in the domain automatically

A second way to do this can be directly done from Microsoft Windows NT environnement, using the administrator priviledged account. This procedure will create automatically an account for the comuter, and will also join it to the domain.

To do so, follow the same steps as the previous section described in section 10.2.1. When informing the domain name, ask for creating a new computer account, and add the administrator account For Microsoft Windows NT 2000, the account is asked when prssing the "ok" button.

10.3  Servers integration

10.3.1  Samba Member Server

TODO: explain configuration

The smb.conf of this Samba member server should indicate: 
; Samba Domain Member server
; like the Samba-LDAP PDC but without security user and LDAP directives, but
; the followin lines:
security = domain
password server = hostname.fqdn (or IP address) of the Samba-LDAP PDC
; note: this samba server does not need to be compiled with 
; --with-ldapsam option

Once configured and started, you should add the machine account on the PDC, using the following commands: 
root@on-the-PDC# smbldap-useradd -w short-hostname-of-the-samba-member-server
and then, on the Samba member server itself: 
root@on-the-member-server# smbpasswd -j "IDEALX-NT"

10.3.2  Samba BDC Server

TOD0: explain. explain alternatives

10.3.3  Microsoft Windows NT Member Server

TODO: explain

10.3.4  Microsoft Windows NT BDC Server

TODO: explain why not :-)

10.3.5  Windows 2000 Member Server

TODO: explian

10.3.6  Windows 2000 BDC Server

TODO: explain why not :-)

11  Migration

In this section, we'll describe how to migrate from a Microsoft Windows NT PDC Server to a Samba+LDAP Domain Controler, in two different user cases: In both cases, emphasis must be placed on transparency of migration: movement to the new system (Samba+LDAP) should be accomplished with the absolute minimum of interference to the working habits of users, and preferably without those users even noticing that is has happened, if feasible.

In both cases, migration concern the following informations:
  1. users accounts (humans and machines),
  2. groups and group members,
  3. users logon scripts,
  4. users profiles (NTUSER.DAT),
  5. all datas,
  6. all shares and shares permissions informations,
  7. all NTFS ACLs used by users on shares.

11.1  General issues

In this example, we'll suppose that we want to migrate a NT4 domain defined with :

11.1.1  Users, Groups and machines accounts

Let's have a look on the different steps needed to migrate all the accounts...

11.1.2  Logon scripts

Logon scripts are DOS scripts that are run every time someone logs on. They must be placed on the [netlogon] special share, and you can specify, for each user, the location of this script in the sambaScriptPath LDAP attribute.

For example, if your special netlogon share is defined like the following example in your /etc/samba/smb.conf configuration file: 
        comment = Network Logon Service
        path = /data/samba/netlogon
        guest ok = Yes

And you want the user myuser to execute the script named myuser.cmd, just complete the following operations: So, to migrate all logons scripts from the old Microsoft Windows NT PDC to the new Linux server, just copy all logon script