Below you will find links to download the binary packages and source files. Please see the FAQ section on Open Source for more information.
After you have installed packages for your system as below, see our install guide for what’s next.
dnf install 389-ds-base
If you want to use the cockpit web ui:
dnf install cockpit-389-ds
zypper install 389-ds
In CentOS 8.1+ directory server is distributed as a module in EPEL 8 (see Modularity documentation for more information). There are three streams available:
stable- rebuild of 389-ds-base package from the oldest of the currently supported releases of Fedora. Recommended version to use.
testing- rebuild of 389-ds-base package from the latest of the currently supported releases of Fedora. A preview of the new features that will be in the next stable release.
next- rebuild of 389-ds-base package from Fedora Rawhide, bleeding edge development version. NOT RECOMMENDED to be used in production, for testing purposes only.
testing streams have 3 profiles:
default- 389-ds-base and cockpit web ui
minimal- just 389-ds-base
legacy- same as default plus legacy perl tools and scripts
next has only
yum install epel-release # make sure you have the latest epel-release that contains modular repositories yum update epel-release yum module install 389-directory-server:stable/default
NOTE: Use the 389-ds-base package from your base distribution. 389-ds-base is part of RHEL and CentOS now. The copr repositories are discontinued.
For the admin server and console parts, you must first install EPEL from https://fedoraproject.org/wiki/EPEL.
Then you can install 389-ds-base and get all of the core directory server, admin server, and console components as per the directions below.
yum install 389-ds-base setup-ds.pl
yum install 389-ds-base 389-admin 389-ds-console 389-admin-console setup-ds-admin.pl
Do a system upgrade as advised by your vendor. That’s it!
This is an Active Directory “plug-in” that intercepts password changes made to AD Domain Controllers and sends the clear text password over an encrypted connection (SSL/TLS) to 389 DS to keep the passwords in sync. It works in conjunction with the Windows Sync feature of 389. You must install this on every Writable Domain Controller. RODCs do not function the same way, so you should not install this plugin on them.
Tested with Windows 2008 and 2012 Server 32-bit and 64-bit.
|Windows 2003/2008 32-bit||389-PassSync-1.1.5-i386.msi||4b79578e3d4bf9cdaada70e5c1212290a4e5ce3c||yes||no [*]|
|Windows 2003/2008 64-bit||389-PassSync-1.1.5-x86_64.msi||ddac9705d305b14fa217af2f264d3529d3f3edb8||yes||no [*]|
|Windows 2003/2008/2012/2016 32-bit||389-PassSync-1.1.7-i386.msi||780e403335a74ea58dc097fb60fd481c8457e105||no [**]||yes|
|Windows 2003/2008/2012/2016 64-bit||389-PassSync-1.1.7-x86_64.msi||0d598943ecdd17eeca2d66174de18d9885951699||no [**]||yes|
[*] 389-PassSync-1.1.5 has no support TLSv1.1 and newer.
[**] 389-PassSync-1.1.7 disables SSLv3 by default.
NOTE: You must use 64-bit Java 7 with the 64-bit version.
Tested with Java 7 on Windows 2008/2012 Server.
|Windows 2008/2012 32-bit||389-Console-1.1.18-i386.msi||eff6e9c34300fa9bd2141944655925aaf5c0b431|
|Windows 2008/2012 64-bit||389-Console-1.1.18-x86_64.msi||39357d69fd45df28657f1f2c73e23dbc552ecd31|
NOTE: You must have Java in your PATH in order for this to work. Or you can just edit the batch file to tell it where to find Java.
Checkout our scripts page here
Checkout our schema page here
We maintain a the project logos and some other nice images.
These works are licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.