389 Directory Server

From Wikipedia, the free encyclopedia
389 Directory Server
Developer(s)Red Hat
Initial releaseDecember 8, 2005; 17 years ago (2005-12-08)
Stable release
2.0.5 / May 30, 2021; 21 months ago (2021-05-30)
Written inC, Python, Perl
Operating systemLinux / Unix
TypeDirectory server
Websitewww.port389.org Edit this on Wikidata

The 389 Directory Server (previously Fedora Directory Server) is a Lightweight Directory Access Protocol (LDAP) server developed by Red Hat as part of the community-supported Fedora Project. The name "389" derives from the port number used by LDAP.

389 Directory Server supports many operating systems, including Fedora, Red Hat Enterprise Linux, Debian, Solaris, and HP-UX 11i.[citation needed] In late 2016 the project merged experimental FreeBSD support.[1] However, the 389 Directory Server team, as of 2017, is likely to remove HPUX and Solaris support in the upcoming 1.4.x series.[2]

The 389 source code is generally available under the GNU General Public License version 3; some components have an exception for plugin code, while other components use LGPLv2 or Apache. Red Hat also markets a commercial version of the project as Red Hat Directory Server as part of support contracts for RHEL.


389 Directory Server is derived from 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.[3][4]

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.[5]


389 Directory server is a rfc4511 compliant server.[6] The project has a focus on ease of use, stability, correctness and performance.[7]

Supported RFCs[edit]

This is a subset of the RFCs that 389 Directory Server supports.

RFC Description
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[edit]

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


See also[edit]


  1. ^ "Support 389-ds on FreeBSD 10.2". Retrieved 2017-04-07.
  2. ^ "389 users mailing list - hpux usage". Retrieved 2017-04-07.
  3. ^ "389 Directory Server Wiki: "What parts are open source?"". Retrieved 2009-07-20.
  4. ^ "389 Directory Server Wiki: "Licensing"". Archived from the original on 2012-02-24. Retrieved 2009-07-20.
  5. ^ "389 Directory Server name change?". Retrieved 2015-09-11.
  6. ^ Sermersheim, J. (2006). Sermersheim, J (ed.). "IETF RFC 4511". doi:10.17487/RFC4511. Retrieved 2017-04-07. {{cite journal}}: Cite journal requires |journal= (help)
  7. ^ "The next year of Directory Server". Retrieved 2017-04-07.
  8. ^ "389 Directory Server RFC support list". Retrieved 2017-04-07.
  9. ^ "389 Directory Server Feature Designs". Retrieved 2017-04-07.

External links[edit]