Sun Java(TM) System Directory Proxy Server 5.2 2005Q1 Release Notes

These Release Notes contain important information available at the time of release of Sun Java System Directory Proxy Server 5.2 2005Q1. New features and enhancements, known issues and limitations, and other information are addressed here.

Use this document if you plan to update to Directory Proxy Server 5.2 2005Q1, or if you are already running Directory Proxy Server 5.2 2005Q1.

The most up-to-date version of these release notes can be found here: http://docs.sun.com/db/coll/DirectoryProxyServer_05q1. Check the web site prior to updating to Directory Proxy Server 5.2 2005Q1 and then periodically thereafter to view the most up-to-date release notes and product documentation.

Third-party URLs are referenced in this document and provide additional, related information.



Note	Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

Release Notes Revision History

Table 1 Revision History
Date	Description of Changes
Feb 2, 2005	Revenue release
Feb 17, 2005	Updated patch version number for localized Solaris patches in Table 6.
Feb 22, 2005	Updated patch version numbers in Table 6 through Table 9 and added support for Solaris 10.

About Directory Proxy Server 5.2 2005Q1

In some parts of the Directory Proxy Server documentation and console, the version number of the product is referred to as 5.2. Directory Proxy Server 5.2 2005Q1 is a maintenance release of Directory Proxy Server 5.2.

What's New in This Release

No new features have been introduced in this release of the product. For information about the bugs fixed in Directory Proxy Server 5.2 2005Q1, see "Bugs Fixed in This Release" on page 4.

Hardware and Software Requirements

The following hardware and software are required for this release of Directory Proxy Server.

Table 2 Solaris SPARC^® Hardware and Software Requirements
Component	Platform Requirement
CPU	Solaris 8 SPARC Platform Edition with patches required for Java Enterprise System Solaris 9 SPARCPlatform Edition with patches required for Java Enterprise System Solaris 10 SPARC Platform Edition with patches required for Java Enterprise System
RAM	256 MB
Disk space	Approximately 300 MB of disk space for a minimal installation.
Patches or service packs	See http://sunsolve.sun.com
Java	Java Runtime Environment 1.5.

Table 3 Solaris x86 Hardware and Software Requirements
Component	Platform Requirement
CPU	Solaris 9 x86 Platform Edition Solaris 10 x86 Platform Edition
RAM	256 MB
Disk space	Approximately 300 MB of disk space for a minimal installation.
Patches or service packs	See http://sunsolve.sun.com
Java	Java Runtime Environment 1.5.

Table 4 Linux Hardware and Software Requirements
Component	Platform Requirement
Operating System	RedHat Advanced Server 2.1 Update 2 or RedHat Advanced Server 3.0 Update 3
Patches or service packs	See http://sunsolve.sun.com
Java	Java Runtime Environment 1.5.
Compatibility libraries	The following compatibility libraries: compat-gcc-7.3-2.96.128.i386.rpm compat-gcc-c++-7.3-2.96.128.i386.rpm compat-libstdc++-7.3-2.96.128.i386.rpm If you running 64-bit Linux, you must install the system libraries for 32-bit Linux.

Bugs Fixed in This Release

The following table describes the bugs fixed in Directory Proxy Server 5.2 2005Q1 since Directory Proxy Server 5.2 2004Q2. For the release notes of Directory Proxy Server 5.2 2004Q2, see http://docs.sun.com/db/doc/817-6253-10.

Table 5 Bugs Fixed in Directory Proxy Server 5.2 2005Q1
Bug Number	Bug Synopsis
4940286	Incorrect Character in Title of French Localization of Directory Proxy Server Console
5041832	Error Message Is Produced the First Time the Console Is Launched for a New Instance
5047201	Japanese On-line Help is Incoherent If Administration Server Help Is Accessed Before Directory Proxy Server Help
5065752	Bind and Unbind stress with ldclt fails on high performance windows platforms
5091854	Referrals hangs with ldapfwd 5.2.09
5091862	IP Connection Limit Is Not Enforced
5105442	Persistent search does not return an error code referred sub suffix

Important Information

This section contains the latest information that is not contained in the core product documentation. This section covers the following topics:

Installation Notes

This section provides notes for installing or migrating to Directory Proxy Server 5.2 2005Q1.

If you are not running any version of Directory Proxy Server, install Directory Proxy Server 5.2 2005Q1 by using the Java Enterprise System Installation Guide.

If you are running Directory Access Router version 5.0 or 5.0 SP1, update to Directory Proxy Server 5.2 2005Q1 by following the recommendations in the chapter called "Migrating System Components from Past Versions" in the Sun Java Enterprise System 2005Q1 Installation Guide.

If you are running Directory Proxy Server 5.2 or 5.2 2004Q2, update to Directory Proxy Server 5.2 2005Q1 by using information in the README file provided with the Directory Proxy Server 5.2 2005Q1 distribution. Use the patch numbers given in Table 6 to Table 9.

Patch Requirements

The following table summarizes the patches required to update Directory Proxy Server 5.2 2004Q2 to Directory Proxy Server 5.2 2005Q1. To access the patches, go to http://sunsolve.sun.com.


Caution	To avoid breaking product dependencies, it is mandatory to install the patches in the order provided in the following tables.

Table 6 Directory Proxy Server 5.2 2005Q1 Alignment Patches Required For Solaris 8 (SPARC)
Patch Number	Patch Description
116103-06	SunOS 5.8: International Components for Unicode Patch
117722-10	SunOS 5.8: NSPR 4.5.1 / NSS 3.9.5 / JSS 4.0
115328-01	SunOS 5.8: Simple Authentication and Security Layer (2.01)
115610-18	SunOS 5.9_sparc: Administration Server 5.2 patch
116837-02	LDAP CSDK - SUNWldk
117017-06	Patch for localized Solaris packages
116373-14	Directory Proxy Server 5.2 Patch

Table 7 Directory Proxy Server 5.2 2005Q1 Alignment Patches Required For Solaris 9 (SPARC)
Patch Number	Patch Description
114677-08	SunOS 5.9: International Components for Unicode Patch
117724-10	SunOS 5.9: NSPR 4.5.1 / NSS 3.9.5 / JSS 4.0
115342-01	SunOS 5.9: Simple Authentication and Security Layer (2.01)
115610-18	SunOS 5.9_sparc: Administration Server 5.2 patch
116837-02	LDAP CSDK - SUNWldk
117017-06	Patch for localized Solaris packages
116373-14	Directory Proxy Server 5.2 Patch

Table 8 Directory Proxy Server 5.2 2005Q1 Alignment Patches Required for Solaris 9 (x86)
Patch Number	Patch Description
114678-08	SunOS 5.9_x86: International Components for Unicode Patch
117725-10	SunOS 5.8: NSPR 4.5.1 / NSS 3.9.5 / JSS 4.0
115611-18	SunOS 5.9_x86: Administration Server 5.2 patch
116838-02	LDAP CSDK - SUNWldk
117017-06	Patch for localized Solaris packages

On Linux systems, the alignment patches include the Directory Proxy Server patch available on http://sunsolve.sun.com and shared component patches, which are provided on the distribution CD. See "Applying Linux Shared Component RPMs" in the Sun Java Enterprise System 2005Q1 Upgrade and Migration Guide for information on locating and installing the RPMs.

Table 9 Directory Proxy Server 5.2 2005Q1 Alignment Patches Required for Linux
Patch Number	Patch Description
118096-04	sun-directory-proxy-server-5.2-9.i386.rpm sun-directory-proxy-server-man-5.2-3.i386.rpm
	sun-icu-2.1-6.i386.rpm sun-sasl-2.02-2.i386.rpm sun-nspr-4.5.1-2.i386.rpm sun-nss-3.9.5-1.i386.rpm sun-ldapcsdk-5.12-3.i386.rpm sun-jss-4.0-5.i386.rpm sun-ljdk-4.17-3.i386.rpm sun-admin-server-5.2-13.i386.rpm sun-server-console-5.2-13.i386.rpm

Configuring Directory Proxy Server For SSL/Certificates

Finding the Installation Log Files

For information about the log files generated during installation, see the following table:

Table 10 Location of Installation Log Files
Platform	Log (administrator/root)	Log (administrator/root)
Solaris	/var/sadm/install/logs	/var/tmp
Solaris x86	/var/sadm/install/logs	/var/tmp
Linux	/var/tmp	/var/tmp

Documentation Notes

Known Issues and Limitations

This section contains a list of the known issues and limitations with Directory Proxy Server 5.2 2005Q1.

After Startup Directory Proxy Server Does Not Automatically Listen on the Network (#4818122)

When Directory Proxy Server is started by the command line, it does not automatically listen on the network. If SSL mode is activated, you must provide a token and password to start SSL. When the token request has been satisfied, Directory Proxy Server can listen on the network.

Cannot Rename an Object With a Previously Used Name (#4863003)

An object cannot be renamed with a previously used name. For example, an object cannot be named and renamed as follows:

This limitation applies to all named properties of the object, including the configuration name.

Using the Log Property Panel on Directory Proxy Server Console Can Corrupt Configuration (#4864081 and #4942337)

Changing the log properties by using the log property panel on the Directory Proxy Server console can corrupt the configuration in the configuration directory server. This issue is caused because the console does not generate an ids-proxy-con-include-logproperty entry in the configuration.

Workaround
Manually generate a new configuration by performing the following procedure:

Export the configuration in the configuration directory server by using the dpsconfig2ldif command.

In the LDIF file, comment out the line that contains the ids-proxy-con-include-logproperty. For example:

#ids-proxy-con-include-logproperty in the entry dn: ids-proxy-con-config-name=myhost , ou=system, ou=dar-config, o=NetscapeRoot

Delete the old system configuration. For example:

ldapdelete -D "cn=Directory Manager" -w password -h dshost -p 389 "ids-proxy-con-config-name=myhost,ou=system, ou=dar-config, o=NetscapeRoot"

Where myhost is the Directory Proxy Server host.

Import the configuration to the configuration directory server by using the dpsldif2config command. For example:

./dpsldif2config -C dps-myhost -h dshost -p 389 -D "cn=Directory Manager" -w password -v ./conf.ldif

Try again to change the log properties by using the log property panel on the Directory Proxy Server console.

On-Line Help Can Fail if Several Directory Proxy Server Instances Are Registered (#4869580)

To display on-line help, the Directory Proxy Server Console contacts any Directory Proxy Server instance registered in the configuration directory. If there is more than one Directory Proxy Server instance registered in the configuration directory, is not possible to specify which Directory Proxy Server instance is used.

If the instance of Directory Proxy Server that answers the request for on-line help is not available, the request fails. The Directory Proxy Server Console does not know that there is no return value and no thrown exception.

Duplicate Configurations Caused by Renaming Configurations With the Console (#4923242)

If you use the Directory Proxy Server Console to rename a Directory Proxy Server configuration a duplicate configuration name is created.

Workaround
To clone a configuration, create a new configuration and copy all of the values from the original configuration to the new configuration.

BIND/UNBIND Is Performed for Each Referral (#4943985)

Instead of reusing existing connections to the backend LDAP servers, Directory Proxy Server performs a BIND/UNBIND for each referral. This issue causes a reduction in performance if the backend server is on a Wide Area Network.

Cannot Follow Referrals in BIND Requests (#4951403)

When a bind request is made by the Directory Proxy Server to another server, a DN is returned. However, the Directory Proxy Server does not use the returned DN to connect to the server. Instead, the Directory Proxy Server uses the original DN. The bind request does not work.

Workaround
This feature is a limitation for bind requests only. This feature is not a limitation for search requests, modify requests, and other requests.

Remote Instance Fails to Start From the Console When SSL Is Enabled (#4961059)

When SSL is enabled in a remote instance of Directory Proxy Server, you cannot use the console to start or restart the instance. The console displays a message that there is no PIN file present.

Workaround
Install a PIN file on the console side, using the same path that is used server side.

Large Entries Are Truncated When Retrieved Over SSL (#4993108)

Backout Fails if Administration Server Is Backed Out Before Directory Proxy Server (#5015762)

Backout fails if Administration Server is backed out before Directory Proxy Server.

Workaround
Back out of Directory Proxy Server before backing out of Administration Server. For more information about updating and backing out of Directory Proxy Server, see the Java Enterprise System Installation Guide.

Must Use Utility Scripts in the Server Root Directory Only (#5033742)

Versions of the utility scripts, dpsconfig2ldif, dpsldif2config, and migratefromidar50 can exist in directories other than the server root directory. However, these versions of the utility scripts might not be correct.

Workaround
Use the utility scripts from this directory only: <serverroot>/bin/dps_utilities.

Migration Fails From IDAR 5.0 or 5.0 SP1 to Directory Proxy Server 5.2 2004Q2 and Later Versions (#5037424)

The migratefromidar50 script fails when migrating from Directory Access Router 5.0 or 5.0 SP1 to Directory Proxy Server 5.2 2004Q2 and later versions. The failure occurs because the password is encrypted in the tailor.txt file for instances of Directory Proxy Server 5 2004Q2 and later versions.

Workaround
1) Replace the encrypted password by the non-encrypted password in the tailor.txt file for the the instance of Directory Proxy Server 5.2 2004Q2 or later version.

Cannot Start Directory Proxy Server Console (#5041840)

If the Administration Server is started before the Configuration Directory Server after installation, the Directory Proxy Server cannot access the Administration Server. In this scenario, the Directory Proxy Server console cannot be started correctly.

Workaround
Start the Configuration Directory Server before starting the Administration Server.

The Console Blocks When a New Instance Is Created (#5042362)

When you create a new instance of Directory Proxy Server, the console blocks and produces this error message: "An error occurred while loading data for this view".

Workaround
Exit from the console or restart the console when you create a new instance.

Redistributable Files

Sun Java System Directory Proxy Server 5.2 2005Q1 does not contain any files which you can redistribute.

How to Report Problems and Provide Feedback

If you have problems with Sun Java System Directory Proxy Server, contact Sun customer support using one of the following mechanisms:

So that we can best assist you in resolving problems, please have the following information available when you contact support:

Description of the problem, including the situation where the problem occurs and its impact on your operation

Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem

Detailed steps on the methods you have used to reproduce the problem

Any error logs or core dumps

You might also find it useful to subscribe to the following interest groups, where Sun Java System Directory Proxy Server topics are discussed:

Sun is interested in improving its documentation and welcomes your comments and suggestions. Use the web-based form to provide feedback to Sun:

Please provide the full document title and part number in the appropriate fields. The part number can be found on the title page of the book or at the top of the document, and is usually a seven or nine digit number. For example, the part number of this Directory Proxy Server 5.2 Release Notes is 817-7614-10.

Additional Sun Resources

Useful Sun Java System information can be found at the following Internet locations:

Sun Java System Documentation
http://docs.sun.com/prod/sunone

Sun Java System Professional Services
http://www.sun.com/service/sunps/sunone

Sun Java System Software Products and Service
http://www.sun.com/software

Sun Java System Software Support Services
http://www.sun.com/service/sunone/software

Sun Java System Support and Knowledge Base
http://www.sun.com/service/support/software

Sun Support and Training Services
http://training.sun.com

Sun Java System Consulting and Professional Services
http://www.sun.com/service/sunps/sunone

Sun Java System Developer Information
http://sunonedev.sun.com

Sun Developer Support Services
http://www.sun.com/developers/support

Sun Java System Software Training
http://www.sun.com/software/training

Sun Software Data Sheets
http://wwws.sun.com/software

Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.

Sun Microsystems, Inc. détient les droits de propriété intellectuels relatifs à la technologie incorporée dans le produit qui est décrit dans ce document. En particulier, et ce sans limitation, ces droits de propriété intellectuelle peuvent inclure un ou plus des brevets américains listés à l'adresse http://www.sun.com/patents et un ou les brevets supplémentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.

Cette distribution peut comprendre des composants développés par des tierces parties.

Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie.

Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.

Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.

Sun Java™ System Directory Proxy Server Release Notes

Version 5.2 2005Q1