Free ldap sync active directory software for linux

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.

PHP Active Code Library (ACL) is a PHP 5 class used to store and call PHP files that are stored in a database.

The files are stored in a plain text field and not a binary field. PHP ACL also takes care of include/require calls.

If a file includes another file stored in the database, PHP ACL takes care of getting, generating, and including that file.

With this service menu you will be able to search into directory by right-clicking on it. Search Into Directory starts a kfind window (part of kdebase) ready to search into the selected directory.

Note : This servicemenu is in fact duplicated of an existing one on kde-apps. So Ive removed mine and I wont maintain it. Youll find another one named Find in Folder

Linbox Directory Server (LDS), along with the Linbox Management Console (LMC), is a powerful system that allows developers, system administrators, and other software vendors to manage users, groups, and their associated policies in an LDAP server.
Linbox Directory Server is highly ergonomic interface design makes it very easy to use, and delegation of administration enables medium size organization to adopt LDS.
Enhancements:
- New features and improvements include DNS/DHCP management and a Norwegian translation.
- The new DNS/DHCP module allows you to manage DNS zones and DHCP subnets for a typical LAN environment.

t@b Directory Uploader is a software that can upload a directory to a FTP server.

You can upload a complete directory to an FTP server, including all subdirectories from a user-friendly interface. Features automatic (no user input required) retry until all files have successfully uploaded.

This program runs on Mac OS X, Windows and Linux

Example:

FTP Host Name: ftp.website.com (no ftp://)
FTP Host Path: foldername (if no folder type / instead)
FTP User Name: ftpusername
FTP Password: ftppassword

LDAP Shell is an interactive LDAP shell written in Perl and allowing basic administrative functionality, such as crawling the directory tree and modifying entries.
It is composed of two parts: Net::LDAP::Config, and ldapsh.
Net::LDAP::Config is a library for simplifying and centralizing access to your LDAP repositories. Instead of having every single script ask for your ldap server and search base, or have it hard coded, you can simply use this library:
my $config = Net::LDAP::Config->new("default");
Its got a couple other nice features, like the fact that it caches your LDAP UID (per host), so you should only ever have to type it in once. Its pretty well documented, so perldoc Net::LDAP::config should get you the rest of the way.
ldapsh, and its corresponding library Net::LDAP::Shell, provide (shockingly) the shell behaviour. When run, ldapsh drops you into a (very simple) interpreter.
Even given its simplicity, though, ldapsh is still very useful: You can use it to walk your LDAP tree, you can clone existing objects (using the clone command), remove objects (can you guess the command?), and create new objects using new.
The new command, when provided one or more objectclasses, will automatically retrieve the required and optional attributes for those objectclasses, which can be a great time-saver.
Enhancements:
- A lot of cleanup, some new commands, and Term::ReadKey support.

YALA is a web-based LDAP administration GUI. The idea is to simplify the directory administration with a graphical interface and neat features, though to stay a general-purpose program (unlike some LDAP browsers written specifically for managing users on the system).
Yet Another LDAP Administrator goal is to simplify the administration but not to make the YALA user stupid: to achieve this, we try to show the user what YALA does behind the scenes, what it sends to the server (unlike Microsoft Active Directory, for example).
Main features:
- Clear and Simple interface
- Cross-Platform: YALA can be accessed from any platform using any modern browser
- Cute javascript to improve the web-interface, which can be set off if you would like
- Theoretically works with any LDAP server, see README file for list of supported LDAP servers.
- Reads the schema from the LDAP server and gets lots of useful information off there.
- Entry Types recognition: You can configure YALA to recognize an entry of objectclasses X & Y, for example, as a user entry, have a special icon for it, and allow simple creation of new entries of this type (i.e. add a new user).
- Its free (under the GPL)

Active Objects is an implementation of the Active Object concept based on the boost::thread, boost::bind, and boost::function libraries.
The point of the library is to make taking advantage of multiprocessor machines as easy as possible. The library provides two types of functionality. The first is the ability to execute a function in a separate thread and automatically synchronize with the thread when the return value is needed.
The second is the ability to easily create a message cue for any existing class, and have that class process its messages asynchronously.
Enhancements:
- Minor code cleanup and code documentation updates.