Samba & LDAP
Fedora Directory Server
Fedora Directory Server has a wiki page on integrating with Samba. See 
OpenLDAP is a widely used LDAP server in Linux environments. It can do a lot of things for all sorts of needs. Samba can use it as a storage backend for accounts and mappings from Windows (TM) SIDs to unix UID/GID. OpenLDAP can also be used to control mail delivery and other things. You can find OpenLDAP at []
For more information about LDAP and it's uses in authentication, also see:
- http://linuxwiki.riverworth.com/index.php/LDAP_Authentication -- Linux LDAP Authentication (including Samba)
OpenDJ is a extension of the Sun Microsystems' initiated OpenDS project as LDAPv3 compliant directory service developed for the Java platform. OpenDS integration with Samba has been documented on their community page as [PDC server] and [CIFS server]. The same instructions apply for OpenDJ, although OpenDJ also comes with a plugin which syncronizes Samba password attributes with the LDAP password attribute - more information can be found [on the plugin page]]. OpenDJ is available at: [].
Mandriva Directory Server  is a free software that offers a web interface to manage Samba and LDAP services
LAM  - A web frontend to maintain accounts for unix and samba in an ldap server
LUMA  - LDAP browser, utility and more (Python/QT)
ldapadmin [] - Ldap Admin is free Win32 application for managing LDAP directories.
LDAP Browser \Editor [] - A Java tool. It is quite old, but still usefull (I use it every time I have to implement a new LDAP tree)
GOsa  - A general purpose webbased LDAP User- and Groupmanagement Tool. Handles all aspects of samba accounts including mungedDial plus everything commonly related to user and group accounthandling
Apache Directory Studio [] - Apache Directory Studio is an Eclipse based LDAP Browser and Directory client. It includes a LDAP Browser, LDIF Editor, and Schema Editor
Integration into the system
It is not that easy to integrate an LDAP directory into a *NIX system. The most anoying thing is that samba relies on the host OS and thus needs uid/gid for a user. You can store these information in your passwd, but for a consistent setup it is recommended to store these things in your LDAP server too.
Given these you have to configure your OS to use an LDAP server as passwd backend and then let samba use the same as own password storage. This is valid for user, group and machine accounts.
Setting up PAM and NSS to use LDAP
It is quite simple but need changes at two places. You have to change nsswitch.conf and add the keyword 'ldap' to the passwd: and group: lines. Then you have to install the library libnss_ldap from your package system.
In the newer releases (as of 03/2006) pam_unix2 can use ldap servers for lookup. You just have to enable it in /etc/security/pam_unix2.conf. But it needs the /etc/ldap.conf file to get all needed parameters for ldap lookups.
Let Samba use LDAP
- passdb backend = ldapsam:ldap://<your-hostname>
- ldap suffix =
- ldap admin dn
then run smbpasswd -w <ldap-secret> to let samba know the password for the admin dn
Mapping the well known Windows groups to unix groups
net groupmap add --unixgroup=<unix-group> --ntgroup="<windows-group>"
Tools to manage accounts
A good tool set for managing accounts are the smbldap-tools from IDEALX. These tools allow the management of most components which are needed for the accounts. Especially user, machine and group management. The real fortunate is that these tools can be set as scripts in smb.conf parameters.
Before you can use the smbldap-tools you have to configure /etc/smbldap-tools/smbldap.conf and /etc/smbldap-tools/smbldap_bind.conf. All entries have to fit your ldap DIT.
After you have done the correct settings, you have to run smbldap-populate. This is mandantory since the base DIT has to be set up properly.
Add the first user
smbldap-useradd -a <username>
Add the first machine
smbldap-useradd -w <machine>
Debugging your setup
The essential thing to get your setup working is not to do all stuff at the same time. It is better to have a basic but working setup. This setup can be migrated to your desired setup later. Doing it this way ensure that the basic setup works.
- Many errors occure due to simple typing errors of the dn or DIT components. IE look at how your user accounts are created: are they uid=<user> or cn=<user>? This little difference leads to misfunction of your setup.
- Machine accounts also needs unix uid/gid. This is needed cause samba looks up those accounts like a normal user account.
- Your Unix machine can't look up the uid/gid from your ldap server: this can be really simply be debugged with the 'getent passwd' and 'getent group' command (if you have getent)
--rcsu 15:09, 15 April 2006 (CDT)