Free ldap server software for linux

CrossFTP Server is a professional FTP Server for multiple platforms. It is a high-performance, extremely configurable, and most of all a secure FTP server. CrossFTP Server has an easy-to-use GUI for user to configure the servers behavior.
Main features:
- 100% pure Java, free, open source FTP server.
- Multi platform support and multithreaded design.
- User virtual directory, write permission, idle time-out and upload/download bandwidth limitation support.
- You can monitor all the user activities.
- Anonymous login support.
- Both upload and download files are resumable.
- Handles both ASCII and binary data transfers.
- IP restriction support to allow/ban IPs.
- Database and LDAP can be used to store user data.
- All the FTP messages are customizable.
- Implicit/explicit SSL/TLS support.
- MDTM support - your users can change the date-time stamp of files.
- "MODE Z" support for faster data upload/download.
- Easy installation/update by Java Web Start technology.

LDAPab is a Web-based address book for small companies. LDAPab features a public address book which is writable for all company staff and a personal address book for each staff member. LDAPab requires an existing LDAP server to authenticate users.

Apache Directory Server is an embeddable LDAP server implemented in pure Java.
Our primary vision (others also outlined below) is to build an enterprise directory server platform (and its components) where other Internet services snap in to store their data within the directory so they may be managed using LDAP.
From the image above youll see the architecture is designed so services besides LDAP like DNS, DHCP, SLP and Kerberos will snap in. Other services like UDDI can also be implemented and snapped in. These services will use a common networking layer and each can be toggled on and off according to the needs of the environment.
apseda, mina, or sedang are various frameworks used for the common network layer. These services share the common network layer and back their data within the Apache Directory Servers backing stores without any network latency or going through the LDAP line protocol. NTP btw is the only exception and its there to remedy the need for time sync for replication and other time sensitive protocols like kerberos. Its implementation here is intended to prevent any dependency on external infrastructure.
Main features:
- Designed as an LDAP and X.500 experimentation platform. Plugable components and subsystems make ApacheDS extremely modular and ideal for experiments with various aspects of the LDAP protocol.
- The servers frontend is completely separable from its backend and vice-versa making it very flexible for implementing virtual directories, proxy servers and gateways to X.500.
- Several backends can be implemented and plugged into the servers partition nexus. The server supports a BTree based partition out of the box but any backing store can be used to implement a partition so long as it conforms to interfaces.
- The server exposes aspects of administration via a special system backend. LDAP can be used to manage these concerns through the system naming context at ou=system.
- Java based triggers and stored procedures are being implemented.
- Both the backend subsystem and the frontend are separable and independently embeddable.
- The server contains a server side JNDI LDAP provider as the facade for the entire backend subsystem. JNDI operations are directly translated by this provider into operations against the nexus and the target partitions storing server entries.
- The server will use JNDI as the data access API for stored procedures. This will make stored procedures functional within and outside of the server without requiring recompilation.
- The servers networking code, MINA, Multipurpose Infrastructure for Network Applications was designed for pluggable protocol providers, of all sorts and not just LDAP. MINA gives ApacheDS the ability to handle large amounts of concurrency.
- The server uses the Snickers tools and APIs for ASN.1 BER encoding and decoding. These tools are designed for a very small encoding and decoding footprint as well as for use in non-blocking servers. The chunking nature of the BER codec makes the server very efficient while handling encoding and decoding making it more resistant to DoS attacks. This layer is also pluggable with a new experimental Twix provider which is much more efficient. Of course there is the unsupported Snacc4J provider which is no longer maintained.

Bind9 LDAP sdb driver is an attempt at an LDAP back-end for BIND 9 using the new simplified database interface "sdb". Using this you can store zones in LDAP rather than in files.

Note that when using sdb, the zones are not cached in memory, BIND will do a database lookup whenever it gets a query. If you want to store zones in LDAP but still have BIND do caching, you may be interested in the ldap2zone tool.

pam_ldap module provides the means for Solaris and Linux servers and workstations to authenticate against LDAP directories, and to change their passwords in the directory.
Main features:
- Uses the Pluggable Authentication Module API defined in OSF DCE RFC 86.0.
- Can utilize transport layer security (such as SSL or TLS) to encrypt transactions between the workstation and the LDAP server and provide strongly authenticated sign-on
- Support for SASL interactive authentication for strong authentication without the overhead of SSL/TLS
- Shares configuration information with nss_ldap module
- Supports PADL NIS/LDAP Gateway locator for finding LDAP servers
- Supports Netscape and IETF password policies
- Supports host- and group-based logon authorization