 | This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages) (Learn how and when to remove this message)
|
| Developer(s) | Red Hat |
|---|---|
| Initial release | December 8, 2005; 19 years ago (2005-12-08) |
| Stable release | 3.1.2 / January 23, 2025; 3 months ago (2025-01-23) |
| Repository | |
| Written in | C,Python,Perl |
| Operating system | Linux /Unix |
| Type | Directory server |
| License | GPL |
| Website | www |
The389 Directory Server (previouslyFedora Directory Server) is aLightweight Directory Access Protocol (LDAP) server developed byRed Hat as part of the community-supportedFedora Project. The name "389" derives from theport number used by LDAP.
389 Directory Server supports many operating systems, includingFedora Linux,Red Hat Enterprise Linux,Debian,Solaris, andHP-UX 11i.[citation needed] In late 2016 the project merged experimentalFreeBSD 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 theGNU General Public License version 3; some components have an exception for plugin code, while other components useLGPLv2 orApache. Red Hat also markets a commercial version of the project asRed Hat Directory Server as part of support contracts for RHEL.
389 Directory Server is derived from the originalUniversity of MichiganSlapd project. In 1996, the project's developers were hired byNetscape Communications Corporation, and the project became known as theNetscape Directory Server (NDS). After acquiring Netscape,AOL sold ownership of the NDSintellectual property toSun Microsystems, but retainedrights 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 thesource code was released asfree software under the terms of theGNU General Public License (GPL).
As of 389 Directory Server version 1.0 (December 1, 2005), Red Hat released asfree software all 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]
This is a subset of the RFCs that 389 Directory Server supports.[8]
| 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 |
In addition to supported RFCS, 389 Directory Server supports a number of features unique to the project.[9]
| 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 |
