Part one of this article discussed the components for a successful directory services migration and how to configure OpenLDAP. In part two, I'll cover how to configure Samba and complete the migration. Make friends with Samba, and your company can dance away from proprietary applications or create a graceful partnership between your open source and proprietary products.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
The Samba server
As discussed above, the Samba server handles incoming authentication requests from Windows clients and negotiates between Windows and OpenLDAP. Let's ignore Samba's general main role (offering file and print services) for the moment; we'll come back to that later in this series.
Before we can use Samba for authentication purposes, we need to prepare OpenLDAP so that Samba can actually perform its role. Again we need to edit the slapd.conf file and include the following:
# Schema files include /etc/openldap/schema/samba.schema
The samba.schema file is part of the Samba package (it does not come with OpenLDAP) and gives OpenLDAP the necessary attributes to authenticate Windows users.
The next step is to set up Samba as a domain controller (something you'd probably want to do in a corporate network anyway) and to configure it to pass Windows' authentication requests to the OpenLDAP server.
The relevant portion of Samba's configuration (in smb.conf) is as follows:
[global] workgroup = YOURCOMPANY netbios name = SERVER1 server string = Samba Server 1 passdb backend = ldapsam:ldap://127.0.0.1/ idmap backend = ldap:ldap://127.0.0.1/ ldap admin dn = cn=Manager,dc=example,dc=com ldap suffix = dc=example,dc=com ldap group suffix = ou=Groups ldap user suffix = ou=Users ldap machine suffix = ou=Computers ldap idmap suffix = ou=Users ldap ssl = no security = user domain logons = yes domain master = no log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_SNDBUF=8192 SO_RCVBUF=8192 dns proxy = No wins support = No preferred master = Yes add user scripts = /usr/local/sbin/smbldap-useradd -m "%u" ldap delete dn = Yes delete user script = /usr/local/sbin/smbldap-userdel "%u" add machine script = /usr/local/sbin/smbldap-useradd -w "%u" add group script = /usr/local/sbin/smbldap-groupadd -p "%g" delete group script = /usr/local/sbin/smbldap-groupdel "%g" [...]
Note that, in the above snippet, we assume that the OpenLDAP server lives on the same system as the Samba server (127.0.0.1) and that we won't use SSL between Samba and OpenLDAP. These and other options, as well as names and locations, should of course be modified as necessary for your installation.
The next step is to make sure that our server knows where to look for users. Edit the nsswitch.conf file as follows:
passwd: files ldap shadow: files ldap group: files ldap hosts: files ldap
As you can see, these entries correspond with the files passwd, shadow, group and hosts in the /etc directory, and each file is referred to LDAP.
When you have your OpenLDAP and Samba servers configured and ready to go, the actual migration should boil down to transferring the contents of your old directory service into the new one and, after testing and verifying that it works correctly, replacing the old server in your network with the new one. This is less trivial than it sounds. As we discussed earlier in this series, it's imperative to thoroughly plan, test and havr a back-out scenario ready in case things don't pan out.
Migrating the data from AD to OpenLDAP would be cumbersome without the right tools. While it is possible to export and import data in several intermediate formats, a direct transfer is preferable. Fortunately such tools are available for download, e.g. from IDEALX. Look for 'Samba' in the Web site's menu and download the smbldap-tools package. Make sure you have the most recent version, because updates are frequent. Use the migration script from this toolkit to transfer the Active Directory contents to OpenLDAP. After the migration is complete, bring the Samba server up. If all is well, your server should now act as a domain controller and replace the old Active Directory server.
The above description is by no means complete. An article such as this is by necessity limited to basic outlines. Fine-tuning a directory server and making sure that all administration tools work properly is not a trivial task. Fortunately many references, how-to's and step-by-step manuals are available on the Internet. Google is your friend.
In-depth textbooks on the subject from major publishers may also prove valuable. After reading up on the details of configuring OpenLDAP and Samba, experiments in a test environment will further familiarize you with the technology.
The next article in this series will discuss Linux-based alternatives to other services. We will deploy Samba to take care of file and print services, and we will take a look at options for messaging, groupware and other intranet-applications, and ERP software.
|About the author: An IT professional for over 15 years, Frank van Wensveen has worked in systems and network administration and implementation, software development, support, engineering and consulting. He currently runs his own IT consultancy and Internet development firm in Johannesburg, South Africa.|