
Configuring Windows Sync
558
Red Hat Directory Server Administrator’s Guide • May 2005
Step 2: Configure SSL on Active Directory (Active Directory only).
To configure SSL on Active Directory, see the appropriate user documentation. It
is not necessary to configure SSL for NT4 Server; SSL is enabled when configuring
the NT4 LDAP Service.
Step 3: Install and Configure the Password Sync Service
Password Sync can be installed on any Windows machine to synchronize
Windows passwords. Passwords can only be synchronized if both your Directory
Server and Windows server are running in SSL, the sync agreement is configured
over an SSL connection, and you have configured certificate databases for
Password Sync to access. See “Installing and Configuring the Password Sync
Service,” on page 550, for information on installing and configuring Password
Sync.
Step 4: Configure the NT4 LDAP Service (Windows NT4 Server Only)
Install the LDAP Service on the Windows NT4 Server, set it up as a Windows
service, and modify the configuration file for your Directory Server information.
See “Installing and Configuring the NT4 LDAP Service,” on page 553, for more
information.
Step 5: Select or Create the Sync Identity
The Windows user specified in the sync agreement, which the Directory Server
will use to bind for sync operations, should be a member of the Domain Admins
group (or have equivalent privileges). A member of this group has full privileges
within the domain, but will not necessarily have privileges within other domains
in the Active Directory deployment. This enhances security by limiting the extent
that the Windows directory can be affected by the sync ID to only the
synchronized subtree.
The user specified in the Password Sync and NT4 LDAP Services should be a a
special user that has write access to entries and passwords but, for security
reasons, should not be Directory Manager. Also, this user should not be under the
synchronized subtree. For information on creating a special sync ID, see “Creating
the Supplier Bind DN Entry,” on page 313.
TIP
It may be useful to lock this admin user from being able to logon to
the domain from a physical location. The entry would be able to
modify the directory entries, but no one could use that entry to gain
access to the domain. Refer the Windows documentation for more
information.
Summary of Contents for DIRECTORY SERVER 7.1
Page 1: ...Administrator s Guide Red Hat Directory Server Version7 1 May 2005 Updated February 2009 ...
Page 20: ...20 Red Hat Directory Server Administrator s Guide May 2005 Glossary 619 Index 635 ...
Page 22: ...22 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 26: ...26 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 78: ...Maintaining Referential Integrity 78 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 200: ...Assigning Class of Service 200 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 488: ...488 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 528: ...PTA Plug in Syntax Examples 528 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 572: ...572 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 612: ...Examples of LDAP URLs 612 Red Hat Directory Server Administrator s Guide May 2005 ...
Page 634: ...634 Red Hat Directory Server Administrator s Guide May 2005 ...