389 Directory Server - Recent changes [en]

Release Procedure

Rmeggins — Tue, 17 Nov 2009 00:14:29 GMT

/* Versioning */

Revision as of 00:14, 17 November 2009		Current revision
Line 1:		Line 1:
	= Versioning =		= Versioning =
	Some background on version numbering is available here - http://en.wikipedia.org/wiki/Software_versioning.		Some background on version numbering is available here - http://en.wikipedia.org/wiki/Software_versioning.
		+
		+	== Naming ==
		+	A full version name will be ''PACKAGENAME'' ''-'' ''VERSIONNUMBER'' e.g. 389-ds-base-1.2.5. The PACKAGENAME part will be the name typically given to the binary package. This name will also be used in the source. For packages that use autoconf for building, this will be the PACKAGE_TARNAME setting. The goal is that the full version name and number used in the source tarball name is the same as the SCM tag name of the tag used to produce that source tarball, and is the same as the name of the binary package. For autoconf packages, this also means the same source tarball name as produced by a ''make dist''.
		+	NAME=<name of package>
		+	VERSION=<version number>
		+	SRCNAME=$NAME-$VERSION
		+	TAG=$SRCNAME
		+
		+	git tag $TAG
		+	git archive --prefix=$TAG/ $TAG \| bzip2 > $SRCNAME.tar.bz2
		+	make dist -> $SRCNAME.tar.bz2
		+	rpmbuild $NAME.spec -> $NAME-$VERSION.<dist>.<platform>.rpm # for RPM platforms
		+
		+	There are a couple of important exceptions to this:
		+	* The DS base and admin packages use an autoconf package name of ''dirsrv'' and ''dirsrv-admin'' - this is the name used to name files and directory paths (e.g. ''/etc/dirsrv''). This is not the same as the name of the source tarballs and binary packages.
		+	* For RPMs, the RPM version number cannot be the same as the source version number for ''pre-release'' builds only, due to the way RPM calculates package dependencies and upgrades - see below

	== Source Version ==		== Source Version ==

Main Page

Rmeggins — Mon, 16 Nov 2009 23:45:51 GMT

Revision as of 23:45, 16 November 2009		Current revision
Line 28:		Line 28:

	==Recent News==		==Recent News==
		+	====389 Windows Password Synchronization 1.1.3 is now available - 389 Windows Console 1.1.4.a1 is now available (November 16, 2009)====
		+	Version 1.1.3 fixes some install issues in 1.1.2. Windows Console 1.1.4.a1 (alpha 1) is now available for testing.
		+	* [[Release_Notes]]
		+	* [[Download]]
		+	* [[Howto:WindowsSync]]
		+	* [[Howto:WindowsConsole]]
		+
	====389 Directory Server 1.2.4 is now available for testing (November 4, 2009)====		====389 Directory Server 1.2.4 is now available for testing (November 4, 2009)====
	We are pleased to announce the availability of 389 Directory Server 1.2.4 for testing. The packages are currently only available from the testing repositories, not the official release repositories. We are seeking feedback. The binary packages available for download will replace the Fedora DS packages with '''389''' branded packages when installed with yum. This release contains 1 new feature and a couple of bug fixes.		We are pleased to announce the availability of 389 Directory Server 1.2.4 for testing. The packages are currently only available from the testing repositories, not the official release repositories. We are seeking feedback. The binary packages available for download will replace the Fedora DS packages with '''389''' branded packages when installed with yum. This release contains 1 new feature and a couple of bug fixes.

Howto:WindowsSync

Rmeggins — Mon, 16 Nov 2009 23:36:06 GMT

/* Configuring PassSync */

Revision as of 23:36, 16 November 2009		Current revision
Line 106:		Line 106:
	=== Configuring PassSync ===		=== Configuring PassSync ===

-	As of version 1.1.2, PassSync supports 32-bit and 64-bit Windows Server 2003 and 2008.	+	As of version 1.1.3, PassSync supports 32-bit and 64-bit Windows Server 2003 and 2008.

	==== Installing PassSync ====		==== Installing PassSync ====
Line 117:		Line 117:
	Follow these steps:		Follow these steps:

-	* Double Click on the PassSync .msi for your platform	+	* Double Click on the PassSync .msi for your platform - see [[Download]]
-	** 32-bit Windows - [http://port389.org/download/389-PassSync-1.1.2-i386.msi http://port389.org/download/389-PassSync-1.1.2-i386.msi]	+
-	** 64-bit Windows - [http://port389.org/download/389-PassSync-1.1.2-x86_64.msi http://port389.org/download/389-PassSync-1.1.2-x86_64.msi]	+
	** You will be asked to provide the following details:		** You will be asked to provide the following details:
	*** 389 Directory Server Hostname		*** 389 Directory Server Hostname

Download

Rmeggins — Mon, 16 Nov 2009 23:35:04 GMT

/* Windows Console */

Revision as of 23:35, 16 November 2009		Current revision
Line 43:		Line 43:
	NOTE: If you are upgrading from version '''1.1.0''', the upgrade will create a new 389 Password Sync folder and copy your files from the old Fedora Password Sync folder. It will not remove the old Fedora Password Sync folder. You can do that manually once you have verified that the new 389 version is working correctly.		NOTE: If you are upgrading from version '''1.1.0''', the upgrade will create a new 389 Password Sync folder and copy your files from the old Fedora Password Sync folder. It will not remove the old Fedora Password Sync folder. You can do that manually once you have verified that the new 389 version is working correctly.

-	NOTE: If you are upgrading from a version older than '''1.1.0''', install the new version first, then remove the old version from the Add/Remove Programs list in the Control Panel. The new version is '''1.1.2'''.	+	NOTE: If you are upgrading from a version older than '''1.1.0''', install the new version first, then remove the old version from the Add/Remove Programs list in the Control Panel. The new version is '''1.1.3'''.

	This is an Active Directory "plug-in" that intercepts password changes made to AD and sends the clear text password to 389 DS to keep the passwords in sync (when using the Windows Sync feature of 389 DS).		This is an Active Directory "plug-in" that intercepts password changes made to AD and sends the clear text password to 389 DS to keep the passwords in sync (when using the Windows Sync feature of 389 DS).
Line 54:		Line 54:
	\|-		\|-
	\| Windows 2003/2008 32-bit		\| Windows 2003/2008 32-bit
-	\| [http://port389.org/download/389-PassSync-1.1.2-i386.msi 389-PassSync-1.1.2-i386.msi]	+	\| [http://port389.org/download/389-PassSync-1.1.3-i386.msi 389-PassSync-1.1.3-i386.msi]
-	\| 4fa651c46426dcf73a9b0faacf7d844485c5b9ad	+	\| fb4fa606877c969b9bec6130a1e81019ff337432
	\|-		\|-
	\| Windows 2003/2008 64-bit		\| Windows 2003/2008 64-bit
-	\| [http://port389.org/download/389-PassSync-1.1.2-x86_64.msi 389-PassSync-1.1.2-x86_64.msi]	+	\| [http://port389.org/download/389-PassSync-1.1.3-x86_64.msi 389-PassSync-1.1.3-x86_64.msi]
-	\| 1a0b84b3f6c952b37c9ca3e17c18d57ff80e0175	+	\| 7e30c5eacc827be663a0eb27f0aed439490a7468
	\|}		\|}

Line 76:		Line 76:
	NOTE: Windows Console now (as of April 3, 2009) requires Java 1.6 to work.		NOTE: Windows Console now (as of April 3, 2009) requires Java 1.6 to work.

-	Tested with Sun Java 1.6 on Windows 2003 Server.	+	NOTE: You must use 64-bit Java with the 64-bit version.
		+
		+	NOTE: This version is 1.1.4.a1 (alpha 1) - alpha releases should be used for testing purposes only
		+
		+	Tested with Sun Java 1.6 on Windows 2008/2003 Server.
	{\| border="1"		{\| border="1"
	! Platform		! Platform
Line 82:		Line 86:
	! SHA1SUM		! SHA1SUM
	\|-		\|-
-	\| Windows	+	\| Windows 2003/2008 32-bit
-	\| [http://directory.fedoraproject.org/download/FedoraConsole-20090403.msi FedoraConsole-20090403.msi]	+	\| [http://port389.org/download/389-Console-1.1.4.a1-i386.msi 389-Console-1.1.4.a1-i386.msi]
-	\| 88d81c551998ae8e001b32c32d1440e2c2795116	+	\| 9b26b03f4fe8a76107bc65689d29232e15ce1af7
		+	\|-
		+	\| Windows 2003/2008 64-bit
		+	\| [http://port389.org/download/389-Console-1.1.4.a1-x86_64.msi 389-Console-1.1.4.a1-x86_64.msi]
		+	\| 1f0387d9a97bc43ee431cf450c8963c2c06f449d
	\|}		\|}
	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. NOTE: This might work with Fedora DS 1.0.4 and earlier, but it has not been tested with that release.		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. NOTE: This might work with Fedora DS 1.0.4 and earlier, but it has not been tested with that release.

Source

Rmeggins — Mon, 16 Nov 2009 23:02:43 GMT

/* 389 Directory Server 1.2.4 */

Revision as of 23:02, 16 November 2009		Current revision
Line 33:		Line 33:
	\| [http://port389.org/sources/389-ds-base-1.2.4.tar.bz2 389-ds-base-1.2.4.tar.bz2]		\| [http://port389.org/sources/389-ds-base-1.2.4.tar.bz2 389-ds-base-1.2.4.tar.bz2]
	\| ds.git \|\| 389-ds-base-1.2.4 \|\| [[Building]] \|\| 54a9257a3b979c5c953e69a45739912f919ebdda		\| ds.git \|\| 389-ds-base-1.2.4 \|\| [[Building]] \|\| 54a9257a3b979c5c953e69a45739912f919ebdda
		+	\|-
		+	\| [http://port389.org/sources/winsync-1.1.3.tar.bz2 winsync-1.1.3.tar.bz2]
		+	\| winsync.git \|\| winsync-1.1.3 \|\| [[Howto:WindowsSync]] \|\| d4b7ee3e75e8fec26bd0a3ebf0f4389d14376529
		+	\|-
		+	\| [http://port389.org/sources/389-console-1.1.4.a1.tar.bz2 389-console-1.1.4.a1.tar.bz2]
		+	\| console.git \|\| 389-console-1.1.4.a1 \|\| [[Howto:WindowsConsole]] \|\| 8fc8616889ef8ef9145fb0198ee02dd5b4b0bcd6
	\|}		\|}
		+
	===389 Directory Server 1.2.3===		===389 Directory Server 1.2.3===
	Modules are git modules and tags are git tags, except where noted as CVS.		Modules are git modules and tags are git tags, except where noted as CVS.

Release Notes

Rmeggins — Mon, 16 Nov 2009 22:59:20 GMT

/* 389 Directory Server 1.2.4 (testing release) - November 4, 2009 */

Revision as of 22:59, 16 November 2009		Current revision
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
		+	== 389 Windows Console 1.1.4.a1 - November 16, 2009 ==
		+	This is the alpha 1 (.a1) release. See [[Release_Procedure]] for information about release numbering. This release supports Windows Server 2008 in addition to 2003. 2000 is no longer supported (although it may work, we don't test it). We also have 64-bit packages in addition to the 32-bit packages.
		+
		+	This release uses the '''389''' branding. The program files folder will be named 389 Management Console.
		+
		+	* Download - [[Download]]
		+	* Howto:WindowsSync - [[Howto:WindowsConsole]]
		+
		+	== 389 Windows Password Synchronization 1.1.3 - November 16, 2009 ==
		+	This release supports Windows Server 2008 in addition to 2003. 2000 is no longer supported (although it may work, we don't test it). We also have 64-bit packages in addition to the 32-bit packages.
		+
		+	This release uses the '''389''' branding. The program files folder will be named 389 Password Sync. If you are upgrading from Fedora PassSync, the upgrade will attempt to copy your db and log files from the Fedora folder to the new 389 folder. It will not remove the old Fedora folder. You can remove that manually after you have verified that the 389 PassSync is working correctly.
		+
		+	* Download - [[Download]]
		+	* Howto:WindowsSync - [[Howto:WindowsSync]]
		+
	== 389 Directory Server 1.2.4 (testing release) - November 4, 2009 ==		== 389 Directory Server 1.2.4 (testing release) - November 4, 2009 ==
	This has been released for testing. The packages are available from the testing repositories, not the official release repositories yet. We are seeking feedback. The new package available for testing is:		This has been released for testing. The packages are available from the testing repositories, not the official release repositories yet. We are seeking feedback. The new package available for testing is:

Howto:WindowsConsole

Rmeggins — Mon, 16 Nov 2009 22:58:07 GMT

Revision as of 22:58, 16 November 2009		Current revision
Line 1:		Line 1:
	==Windows Console==		==Windows Console==
-	Fedora Directory Server provides a console package for use on Windows, in the form of a file called FedoraConsole.msi.	+	389 Directory Server provides a console package for use on Windows. See [[Download]] for the current installable package.

	===Building===		===Building===
Line 10:		Line 10:
	* LDAPJDK JAR		* LDAPJDK JAR
	* idm-console-framework JAR files		* idm-console-framework JAR files
-	* fedora-idm-console JAR file	+	* 389-console JAR file
	* Optional - The Windows Support Tools package for your platform		* Optional - The Windows Support Tools package for your platform
	** The build will use the bitsadmin program from this package to download packages if available		** The build will use the bitsadmin program from this package to download packages if available
	* The nmake command - usually provided with the Visual Studio or Visual C++ or Windows SDK packages		* The nmake command - usually provided with the Visual Studio or Visual C++ or Windows SDK packages

-	Source:	+	Source: [[Source]]
-	* CVS - cvs -d ":pserver:anonymous@cvs.fedoraproject.org:/cvs/dirsec" co -r TAG fedora-idm-console	+
-	** The latest TAG is FedoraIDMConsole_1_1_3	+
-	* tar ball - http://directory.fedoraproject.org/sources/fedora-idm-console-VERSION.tar.bz2	+
-	** The latest VERSION is 1.1.3	+

	Build: The build uses a regular CMD shell - no cygwin, msys, etc. are required.		Build: The build uses a regular CMD shell - no cygwin, msys, etc. are required.
Line 27:		Line 23:
	* nmake download - will attempt to download the prerequisites listed above using bitsadmin from the Support Tools package - it tries to use c:\program files\support tools\bitsadmin		* nmake download - will attempt to download the prerequisites listed above using bitsadmin from the Support Tools package - it tries to use c:\program files\support tools\bitsadmin
	* nmake layout - will create the layout used for packaging		* nmake layout - will create the layout used for packaging
-	* nmake all - will create the FedoraConsole.msi package	+	* nmake all - will create the 389 Console.msi package

-	The FedoraConsole.msi and other files built by nmake will be found in the build.PLATFORM directory, where PLATFORM by default is WINNT5.0_OPT.OBJ.	+	The 389 Console.msi and other files built by nmake will be found in the build.PLATFORM directory, where PLATFORM by default is WINNT5.0_OPT.OBJ.

	===Firewall Information===		===Firewall Information===
Line 48:		Line 44:

	===TLS/SSL===		===TLS/SSL===
-	By default, the console expects your key and cert database files in $HOME/.fedora-idm-console. On Windows, this is usually something like C:\Documents and Settings\<username>\.fedora-idm-console. So when you use the NSS command line utilities like certutil and pk12util, use the -d argument like this:	+	By default, the console expects your key and cert database files in $HOME/.389-console. On Windows, this is usually something like C:\Documents and Settings\<username>\.389-console. So when you use the NSS command line utilities like certutil and pk12util, use the -d argument like this:
-	certutil -A -d "C:\Documents and Settings\<username>\.fedora-idm-console" -n "CA Certificate" -t CT,, -i cacert.asc -a	+	certutil -A -d "C:\Documents and Settings\<username>\.389-console" -n "CA Certificate" -t CT,, -i cacert.asc -a
	for example, to add the CA cert from the file cacert.asc encoded in ASCII (PEM) format. Now your Console running on Windows should be able to use https and ldaps.		for example, to add the CA cert from the file cacert.asc encoded in ASCII (PEM) format. Now your Console running on Windows should be able to use https and ldaps.

Features

Rmeggins — Mon, 16 Nov 2009 22:53:56 GMT

Revision as of 22:53, 16 November 2009		Current revision
Line 3:		Line 3:

	=== Database ===		=== Database ===
-	Fedora Directory Server uses the [http://www.oracle.com/database/berkeley-db/db/index.html Berkeley Database] as its data store. This data store is very high performance and is transacted to ensure ACID data updates. Fedora DS automatically detects if the data was not written cleanly and does a database restore at startup if necessary.	+	389 Directory Server uses the [http://www.oracle.com/database/berkeley-db/db/index.html Berkeley Database] as its data store. This data store is very high performance and is transacted to ensure ACID data updates. 389 DS automatically detects if the data was not written cleanly and does a database restore at startup if necessary.

	==== Multiple databases ====		==== Multiple databases ====
Line 14:		Line 14:

	=== Microsoft Windows Synchronization ===		=== Microsoft Windows Synchronization ===
-	User, group, and password information can be synchronized with an Active Directory (2000 and 2003) domain controller and with an NT4 domain controller.	+	User, group, and password information can be synchronized with an Active Directory (2003 and 2008 34-bit and 64-bit) domain controller and with an NT4 domain controller.

	=== Powerful access control mechanism ===		=== Powerful access control mechanism ===
Line 37:		Line 37:

	==== [[Task_Invocation_Via_LDAP\|Task invocation via LDAP]] ====		==== [[Task_Invocation_Via_LDAP\|Task invocation via LDAP]] ====
-	Fedora DS provides a special entry called cn=tasks,cn=config with several sub-entries for each type of task supported: cn=import; cn=export; cn=backup; cn=restore; cn=index. The creation of an entry under one of these sub-entries causes the directory server to invoke that operation. Parameters are passed to the operation as attributes in the entry (e.g. the name of the LDIF file to export to). Status information is reported as attributes in that entry allowing clients to query for task status and completion.	+	389 DS provides a special entry called cn=tasks,cn=config with several sub-entries for each type of task supported: cn=import; cn=export; cn=backup; cn=restore; cn=index. The creation of an entry under one of these sub-entries causes the directory server to invoke that operation. Parameters are passed to the operation as attributes in the entry (e.g. the name of the LDIF file to export to). Status information is reported as attributes in that entry allowing clients to query for task status and completion.

	=== Password Policy and Account Lockout ===		=== Password Policy and Account Lockout ===
Line 90:		Line 90:

	=== [[DSML_Gateway_Design\|DSML Gateway]] ===		=== [[DSML_Gateway_Design\|DSML Gateway]] ===
-	DSMLv2 is a SOAP/HTTP based protocol for communicating with directory services. Fedora DS provides a gateway that runs apart from the server on a web or application server (such as Tomcat).	+	DSMLv2 is a SOAP/HTTP based protocol for communicating with directory services. 389 DS provides a gateway that runs apart from the server on a web or application server (such as Tomcat).