United States (change)
Shortcuts: Downloads Fedora Red Hat Network
Evaluation Guidelines: |
This page provides links and other information relevant to evaluating Red Hat Directory Server 7.1.
For links to all documentation available online, see the entries listed at the top of this page: Red Hat Directory Server Documentation.
| Background Information and Other Useful Documentation |
Introduction to Directory Services: Overview of LDAP, key terms, and high-level architecture considerations. (From the Red Hat Directory Server Deployment Guide.)
Red Hat Directory Server Installation Guide: Complete installation instructions, including initial preparation, system requirements, and migration guidelines.
Introduction to Directory Server: After you've installed Directory Server, read this chapter for information about the Console interface and basic tasks such as starting and stopping the server. (From the Red Hat Directory Server Administrator's Guide.)
| New Features in Red Hat Directory Server 7.1 |
Replication over a Wide Area Network (WAN): A WAN is typically a set of geographically dispersed networks that include slow, degraded, or poor links. Directory Server 7.1 allows administrators to set up reliable 4-way multi-master replication (MMR) across a WAN as well as a local network.
For details on setting up multi-master replication, see:
File System Replica Initialization: Directory Server 7.1 allows administrators to load data from an existing server into a new replica server. In recent versions of Directory Server, replica initialization had to be done via a network connection between the supplier and consumer, or by exporting the data to a text file and building a new database with it on the replica. These methods are not efficient for very large databases, for example with millions of entries. Directory Server 7.1 adds the ability to initialize a replica using the database files from the supplier server, which can be transferred very quickly at raw network speeds (over FTP or NFS, for example). Because there is some overhead involved in this new manual procedure, the old network and export initialization procedures still work and are recommmended for smaller databases.
See File System Replica Initialization. (From the Red Hat Directory Server Administrator's Guide.)
Fractional Replication: This release makes it possible to replicate a selected subset of all attributes for a replicated suffix; for example, office phone numbers for all employees in the support organization might be replicated, but not their home numbers. Replicating a subset of entries under a given suffix is not supported; for example, replicating only the entries for managers in the support organization will not be posssible.
See Managing Replication. (From the Red Hat Directory Server Administrator's Guide.)
Identity Sync for Windows: This release allows administrators to set up bidirectional password synchronization between the following directories:
See Windows Sync. (From the Red Hat Directory Server Administrator's Guide.)
Password Change Control: Historically, LDAP clients have changed user passwords by modifying an entry's 'userPassword' attribute. However, many other authentication mechanisms (such as the Unix PAM interface) work differently, so this process doesn't achieve good interoperability. Password Change Control RFC 3062 defines a generic extended operation for changing a user's password, regardless of the underlying authentication mechanism. Directory Server 7.1 supports this RFC (see http://www.ietf.org/rfc/rfc3062.txt).
See Password Change Extended Operation. (From the Red Hat Directory Server Administrator's Guide.)
Get Effective Rights Operations: The Get Effective Rights feature allows users who have the necessary rights to find out what access rights to a given portion of the DIT some other user has. For example, if an administrator wants to know whether a particular user has the right to view or change certain attributes in some portion of the tree, Get Effective Rights provides a way to do this. In this release, Red Hat Console provides a UI that simplifies such requests. In addition, the operation is optimized, where possible, for performance when requesting rights for large sets of attributes.
See Get Effective Rights Control. (From the Red Hat Directory Server Administrator's Guide.)