Sun Java System Directory Proxy Server 5 2004Q2 Release Notes

Sun Java™ System Directory Proxy Server Release Notes

Version 5 2004Q2

Part Number 817-6253-10

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

Use this document if plan to update to Directory Proxy Server 5 2004Q2, or if you are already running Directory Proxy Server 5 2004Q2.

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

These release notes contain the following sections:

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

June 13, 2003

Initial publication of these release notes

March 26, 2004

Publication for beta release of Directory Proxy Server 5 2004Q2

May 6, 2004

Publication for revenue release of Directory Proxy Server 5 2004Q2

About Directory Proxy Server 5 2004Q2

On the Directory Proxy Server Console, Directory Proxy Server 5 2004Q2 is sometimes referred to as Directory Proxy Server 5.2. Directory Proxy Server 5 2004Q2 is a maintenance release of Directory Proxy Server 5.2.

This section includes:

What's New in This Release

This version of the Directory Proxy Server contains the following new features:

Hardware and Software Requirements

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

Table 2 Solaris Hardware and Software Requirements 

Component

Platform Requirement

CPU

Solaris 8 SPARC® Platform Edition with patches required for Java Enterprise System

Solaris 9 SPARC® 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

Table 3 Solaris x86 Hardware and Software Requirements 

Component

Platform Requirement

CPU

Solaris 9 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

Table 4 Linux Hardware and Software Requirements 

Component

Platform Requirement

CPU

RedHat Advanced Server 2.1 Update 2

RAM

256 MB

Disk space

Approximately 300 MB of disk space for a minimal installation.

Patches or service packs

None

Bugs Fixed in This Release

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

Table 5 Bugs Fixed in Directory Proxy Server 5 2004Q2 Since Directory Proxy Server 5.2  

Bug Number

Bug Synopsis

4554991

Save button always enabled for OnSSLEstablished Event

4555088

Health check must do more than just connect

4789877

Wrong message if DS not started at DPS startup time

4870271

DPS Topology Configs do not display help under certain conditions

4874761

Daemon doesn't start when SSL configured and token requested on command-line

4891322

ldapfwd generates core during high load with referrals

4892644

SSL referral hangs the client

4894043

Search Referral crashes proxy when configured to discard the reference

4895804

Typo prevents Solaris Native Mode packages from checking dependencies

4919517

DPS does not find component libs

4933448

Directory Proxy Server 5.2 patch 3 crashes when referred-to server is down.

4934980

Cannot unconfigure as non-root (SolPkg)

4935314

Directory Proxy Server crashes during a ldap_modify

4942940

5.2 install fails when running setup as root but specifying non-root user

4966944

Sun ONE Directory Proxy Server 5.2 should use the short length form when possible

4976424

Group change can lead to incorrect load balancing

4984682

Removing one instance unregisters SIEs of all instances in CDS

4984800

Cannot perform search with empty attribute type

4990235

DPS 5.2: attribute renaming doesn't work when filter contains a NOT operator

4992270

Server Load parameters are not consulted when a Change Group operation occurs

4994492

removing a DPS instance may remove certificates of other instances

4997218

Need more details in quickstart.tcl error logs

5006308

RPM: search on secure connection is interrupted

5031413

Cannot access on line help pages from the configurator sub menus

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 2004Q2.

Patch Requirements

The following table summarizes the patches required to update Directory Proxy Server 5.2 to Directory Proxy Server 5 2004Q2.

Table 6 Patches Required for Update From Directory Proxy Server 5.2 to Directory Proxy Server 5 2004Q2

Platform

Required Patch

Solaris

116373-09

Solaris x86

116374-09

If you are upgrading from Directory Proxy Server 5.2 on a Linux platform, you must install Directory Proxy Server 5 2004Q2 from scratch. You can save the configuration of your current installation and load the saved configuration to the new installation.

Configuring Directory Proxy Server For SSL/Certificates

For information about how to configure Directory Proxy Server 5 2004Q2 for SSL-enabled communication, see the Directory Proxy Server 5 2004Q2 Administration Guide.

Finding the Installation Log Files

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

Table 7 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

Compatibility Issues

The LDAP utility man pages on Sun Solaris platforms do not document the Sun Java System version of the LDAP utilities ldapsearch, ldapmodify, ldapdelete, and ldapadd. For information about these utilities, refer to the Sun Java System Directory Server Resource Kit Tools Reference.

Documentation Updates for Directory Proxy Server 5 2004Q2

Directory Proxy Server 5 2004Q2 is now installed by the Sun Java Enterprise System Installer. Information about how to install Directory Proxy Server 5 2004Q2 is contained in the Sun Java System documentation on http://docs.sun.com/db/coll/entsys_04q2. There is no installation guide dedicated to the Directory Proxy Server 5 2004Q2.

Information about how to update from Directory Proxy Server 5.2 to Directory Proxy Server 5 2004Q2 is contained in the README file provided with the Directory Proxy Server 5 2004Q2 distribution.

Known Issues and Limitations

This section contains a list of the known issues.

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.

Workaround
None

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.

Workaround
Always use new name to rename an object.

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

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.

Workaround
None

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.

Workaround
None

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.

Incorrect Character in Title of French Localization of Directory Proxy Server Console (#4940286)

There is an incorrect character in the title of the French localization of the Directory Proxy Server Console.

Workaround
None

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.

Workaround
None

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.

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

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

Workaround
Back out of the Directory Proxy Server 5 2004Q2 before backing out of Administration Server 5 2004Q2. For more information about updating and backing out of Directory Proxy Server, see the Sun Java Enterprise System 2004Q2 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 2004Q2 (#5037424)

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

Workaround
1) Replace the encrypted password by the non-encrypted password in the tailor.txt file for the Directory Proxy Server 5 2004Q2 instance.

2) Launch the migration script.

Error Message Is Produced the First Time the Console Is Launched for a New Instance (#5041832)

The first time that the Directory Proxy Server console is launched for a new instance, the following error message is produced: "unable to open certificate database". The error occurs because the certificate database has not yet been created.

Workaround
Click ok to make the error window disappear, and continue. The default certificate database for the instance is created and the problem will not reoccur for that instance.

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.

Japanese On-line Help is Incoherent If Administration Server Help Is Accessed Before Directory Proxy Server Help (#5042362)

In the Japanese localization of the on-line help, if the Administration Server help is opened before the Directory Proxy Server help the main page of the Directory Proxy Server help is garbled.

Workaround
Open the Directory Proxy Server help before opening the Administration Server help.

Redistributable Files

Sun Java System Directory Proxy Server 5 2004Q2 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 by 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:

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

Sun Welcomes Your Comments

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 is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the part number of these Release Notes document is 817-6253-10.

Additional Sun Resources

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

Copyright © 2004 Sun Microsystems, Inc. All rights reserved.

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.

SUN PROPRIETARY/CONFIDENTIAL.

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.

Use is subject to license terms.

This distribution may include materials developed by third parties.

Portions may be derived from Berkeley BSD systems, licensed from U. of CA.

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.

Copyright © 2004 Sun Microsystems, Inc. Tous droits réservés.

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.

Propriété de SUN/CONFIDENTIEL.

L'utilisation est soumise aux termes du contrat de licence.

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.