389 Directory Server
||This article contains content that is written like an advertisement. (December 2016) (Learn how and when to remove this template message)|
|This article relies too much on references to primary sources. (March 2013) (Learn how and when to remove this template message)|
|Initial release||December 8, 2005|
184.108.40.206 / March 23, 2017
|Written in||C, Python, Java, Perl, shell script|
|Operating system||Linux / Unix|
The 389 Directory Server (previously Fedora Directory Server) is an LDAP (Lightweight Directory Access Protocol) server developed by Red Hat, as part of Red Hat's community-supported Fedora Project. The name "389" derives from the port number used by LDAP. Red Hat offers a version of 389 called Red Hat Directory Server via an extra subscription on top of RHEL. Red Hat Directory Server differs from 389 in that the former is rebranded with the Red Hat branding, and includes certified stable builds, customer service, and technical support. Red Hat will rebase the Red Hat version with a stable upstream 389 branch in line with Red Hat Enterprise Linux releases, and backport new features and critical bug fixes as necessary. The 389 source code is generally available under the GPLv3 license. Some components have an exception for plugin code, while other components use LGPLv2 or Apache. The same applies to Red Hat Directory Server.
389 Directory Server previously supports many operating systems, including Red Hat Enterprise Linux 3 and later, Debian, Solaris 8 and later, and HP-UX 11i. In late 2016 the project merged experimental FreeBSD support.  However, the 389 Directory Server team as of 2017 is likely to remove HPUX and Solaris support in the upcoming 1.4.x series. 
389 Directory Server is the newest incarnation of what was once the original University of Michigan slapd project. In 1996, the project's developers were hired by Netscape Communications Corporation and the project became known as the Netscape Directory Server (NDS). After acquiring Netscape, AOL sold ownership of the NDS intellectual property to Sun Microsystems, but retained rights akin to ownership. Sun sold and developed the Netscape Directory Server under the name JES/SunOne Directory Server, now Oracle Directory Server since the takeover of Sun by Oracle. AOL/Netscape's rights were acquired by Red Hat, and on June 1, 2005, much of the source code was released as free software under the terms of the GNU General Public License (GPL).
As of 389 Directory Server version 1.0 (December 1, 2005), Red Hat released as free software all of the remaining source code for all components included in the release package (admin server, console, etc.) and continues to maintain them under their respective licenses.
In May 2009 the Fedora Directory Server project changed its name to 389 to give the project a distribution and vendor neutral name and encourage porting or running the software on other operating systems.
This is a subset of the RFCs that 389 Directory Server supports.
|1274||COSINE and x.500 schema|
|2222||Simple Authentication and Security Layer|
|2830||Lightweight Directory Access Protocol (v3): Extension for Transport Layer Security (StartTLS)|
|4527||Read Entry Controls|
Non RFC Features
In addition to supported RFCS, 389 Directory Server supports a number of features unique to the project.
|Name of feature||Description|
|MemberOf||MemberOf provides reverse group links from group members|
|Class of Service||Apply virtual attributes from a template to entries|
|Distributed Numeric Assignment||Automatically create uidNumber/gidNumber from server id allocations|
|Multimaster Replication||Allows multiple writeable masters to asynchronously replicate data.|
|Autoscaling||The server automatically scales up and down based on hardware size|
- "Support 389-ds on FreeBSD 10.2". Retrieved 2017-04-07.
- "389 users mailing list - hpux usage". Retrieved 2017-04-07.
- "389 Directory Server Wiki: "What parts are open source?"". Retrieved 2009-07-20.
- "389 Directory Server Wiki: "Licensing"". Retrieved 2009-07-20.
- "389 Directory Server name change?". Retrieved 2015-09-11.
- "IETF RFC 4511". Retrieved 2017-04-07.
- "The next year of Directory Server". Retrieved 2017-04-07.
- "389 Directory Server RFC support list". Retrieved 2017-04-07.
- "389 Directory Server Feature Designs". Retrieved 2017-04-07.