Page History

{scrollbar}
{note:title=Work in progress}
This site is in the process of being reviewed and updated.
{note}
{scrollbar}

{note}
You are viewing pre-release documentation that contains changes to configuration that are scheduled for the Apache Directory 1.5.1 release.{note}


h3. Apache Directory Protocol Providers

The Apache Directory Project's Protocol Providers are Java implementations of standard Internet services. These Protocol Providers, in conjunction with the MINA network layer and the Apache Directory read-optimized backing store, provide easy-to-use yet fully-featured Internet services. As implemented within the Apache Directory, these services benefit from:
* Standard directory model and schema support
* Standard LDAP data interchange format (LDIF) (RFC 2849)
* Optional LDAP management
* UDP and TCP Support (MINA)
* Easy POJO embeddability for containers such as Geronimo, JBoss, and OSGi

h3. Service Configuration

All protocol providers are configured in a similar manner.  Behind the scenes, all protocol provider Configuration beans inherit from the same ServiceConfiguration and, therefore, they share many of the same configuration parameters.  For more information on the service configuration common to all protocol providers, please see [5.2 Common Parameters for Configuration].

h3. Changes from 1.5 to 1.5.1

Configuration has been revamped for the 1.5.1 release, along with the addition of SASL support in the LDAP protocol.  For more information on changes to configuration, please see [5.2.1. Changes to Configuration].

h3. Protocol Providers

|| Name || Configuration || Description ||
| [5.3. LDAP Protocol Provider] | [5.3.1. LDAP Protocol Configuration] | A Lightweight Directory Access Protocol (LDAP) implementation based on {link:RFC 2251|http://www.faqs.org/rfcs/rfc2251.html}. Apache LDAP provides lightweight access to the Apache Directory backing store.|
| [5.4. Kerberos Protocol Provider] | [5.4.1. Kerberos Protocol Configuration] | A Kerberos implementation based on {link:RFC 1510|http://www.faqs.org/rfcs/rfc1510.html}. Apache Kerberos verifies the identities of principals (users or services) on an unprotected network using principal information stored in the Apache Directory backing store.|
| [5.5. Change Password Protocol Provider] | [5.5.1 Change Password Configuration] | A Change Password implementation based on {link:RFC 3244|http://www.faqs.org/rfcs/rfc3244.html}. Apache Change Password uses Kerberos infrastructure to allow users to securely set initial passwords or to change existing passwords stored in the Apache Directory backing store.|
| [5.6. DNS Protocol Provider] | [5.6.1 DNS Protocol Configuration] | A Domain Name System (DNS) implementation based on {link:RFC 1034|http://www.faqs.org/rfcs/rfc1034.html}. Apache DNS serves host name to address mappings and other resource record types using resource records stored in the Apache Directory backing store.|
| [5.7. NTP Protocol Provider] | [5.7.1. NTP Protocol Configuration] | A Network Time Protocol (NTP) implementation based on {link:RFC 2030|http://www.faqs.org/rfcs/rfc2030.html}. Apache NTP supports time synchronization for LDAP replication and the Kerberos protocol, eliminating the need for external infrastructure.|
| [5.8. DHCP Protocol Provider] | n/a | A Dynamic Host Configuration Protocol (DHCP) implementation based on {link:RFC 2131|http://www.faqs.org/rfcs/rfc2131.html}. Apache DHCP helps configure hosts using configuration information stored in the Apache Directory backing store.|