Protocol Provider Subprojects

The Apache Directory Project's Protocol Providers are Java implemen= tations of=20 - standard Internet services. These Protocol Providers, in conjunction w= ith the MINA=20 - network layer and the Apache Directory read-optimized backing store, p= rovide=20 - easy-to-use yet fully-featured Internet services. As implemented withi= n the Apache=20 - Directory, these services benefit from:

Standard directory model and schema support
Standard LDAP data interchange format (LDIF) (RFC 2849)
JMX remote management (JSR 160, JSR 28)
Optional LDAP management
UDP and TCP Support (MINA)
Traffic throttling (MINA)
Overload shielding (MINA)
Easy POJO embeddability for containers such as Geronimo, JBoss, an= d OSGi

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Name	Description
- Lightweight Directory Access Protocol (L= DAP)=20 - Provider -	- An LDAP implementation based on RFC 2251. Apache= LDAP=20 - provides lightweight access to the Apache Directory backing store.<= /p> -
- Kerberos Protocol Provider -	- A Kerberos implementation based on RFC 1510. Apache=20 - Kerberos verifies the identities of principals (users or services) = on=20 - an unprotected network using principal information stored in the Ap= ache=20 - Directory backing store. -
- Change Password Protocol Provider -	- A Change Password implementation based on RFC 3244. Apache=20 - Change Password uses Kerberos infrastructure to allow users to secu= rely=20 - set initial passwords or to change existing passwords stored in the=20 - Apache Directory backing store. -
- Domain Name System (DNS) Protocol Provide= r -	- A DNS implementation based on RFC 1034. Apache= DNS=20 - serves host name to address mappings and other resource record type= s=20 - using resource records stored in the Apache Directory backing store= . -
- Network Time Protocol (NTP) Provider -	- An NTP implementation based on RFC 2030. Apache= NTP=20 - supports time synchronization for LDAP replication and the Kerberos=20 - protocol, eliminating the need for external infrastructure. -
- Dynamic Host Configuration Protocol (DHC= P)=20 - Provider -	- A DHCP implementation based on RFC 2131. Apache= DHCP=20 - helps configure hosts using configuration information stored in the=20 - Apache Directory backing store. -

The Apache Directory Project's Protocol Providers are Java imple= mentations of + standard Internet services. These Protocol Providers, in conjuncti= on with the MINA + network layer and the Apache Directory read-optimized backing stor= e, provide + easy-to-use yet fully-featured Internet services. As implemented w= ithin 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)
Traffic throttling (MINA)
Overload shielding (MINA)
Easy POJO embeddability for containers such as Geronimo, JBoss= , and OSGi

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Name	Description
+ Lightweight Directory Ac= cess Protocol (LDAP) + Provider +	+ An LDAP implementation based on RFC 2251.= Apache LDAP + provides lightweight access to the Apache Directory backing = store. +
+ Kerberos Protocol Pr= ovider +	+ A Kerberos implementation based on RFC 1510.= Apache + Kerberos verifies the identities of principals (users or ser= vices) on + an unprotected network using principal information stored in= the Apache + Directory backing store. +
+ Change Password Prot= ocol Provider +	+ A Change Password implementation based on RFC 3244.= 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. +
+ Domain Name System (DNS) = Protocol Provider +	+ A DNS implementation based on RFC 1034.= Apache DNS + serves host name to address mappings and other resource reco= rd types + using resource records stored in the Apache Directory backin= g store. +
+ Network Time Protocol (NT= P) Provider +	+ An NTP implementation based on RFC 2030.= Apache NTP + supports time synchronization for LDAP replication and the K= erberos + protocol, eliminating the need for external infrastructure.<= /p> +
+ Dynamic Host Configurati= on Protocol (DHCP) + Provider +	+ A DHCP implementation based on RFC 2131.= Apache DHCP + helps configure hosts using configuration information stored= in the + Apache Directory backing store. +