Chapter 6 Directory Editor Bugs Fixed and Known Problems

This chapter contains important, product-specific information available at the time of release of Directory Editor.

This chapter includes the following sections:

• Bugs Fixed in Directory Editor

• Known Problems and Limitations in Directory Editor

Bugs Fixed in Directory Editor

This section lists the bugs fixed since the last release of Directory Editor.

6563224

When creating a new form for a user object class, a form is generated, presenting the object class attributes. The multivalued field is unchecked by default for multivalued attributes.

Known Problems and Limitations in Directory Editor

This section lists known problems and limitations at the time of release.

Directory Editor Limitations

This section lists product limitations. Limitations are not always associated with a change request number.

The following configuration requirements exist for using Directory Editor through Directory Proxy Server.

When configuring Directory Editor to access data through Directory Proxy Server, you must observe the following constraints.

• The Directory Editor configuration directory must be an instance of Directory Server, not Directory Proxy Server.

  You specify the Directory Editor configuration directory when initially configuring Directory Editor through the Startup Properties page. The configuration directory must contain the entry with Bind DN and Password you provide in the Startup Properties page. The configuration directory must also already have the Configuration Suffix whose DN you select in the drop down list of the Startup Properties page.

• All Directory Proxy Server instances through which you access data using Directory Editor must be configured with a data view to allow access to search the directory schema. Schema are stored under cn=schema for Directory Server.

  For example, the following command configures a schema view into the Directory Server instances in My Pool.

  $ dpconf create-ldap-data-view -h localhost -p 1390 "schema view" \ "My Pool" cn=schema Enter "cn=Proxy Manager" password: $

• All Directory Proxy Server instances through which you access data using Directory Editor must be configured to provide access through to the data sources. In particular, the Directory Proxy Server instances must have data views configured to allow the users logging in to Directory Editor at least to bind to the Directory Server data sources.

  For example, the following command configures Directory Proxy Server to allow all LDAP operations through to the attached data source, My DS in My Pool.

  $ dpconf set-attached-ldap-data-source-prop -h localhost -p 1390 \ "My Pool" "My DS" add-weight:1 bind-weight:1 compare-weight:1 delete-weight:1 \ modify-dn-weight:1 modify-weight:1 search-weight:1 Enter "cn=Proxy Manager" password: $

Known Directory Editor Issues

This section lists known issues. Known issues are associated with a change request number.

6257547

Directory Editor displays a configurable number of results for a search, with the default being 25. If a search returns more entries than the maximum number to display, refine the search to return fewer results.

6258793

When deploying on Sun Java Enterprise System Application Server 8, an error file is written. Also, login fails.

To work around this issue, ensure the following grant statement is included in the Server.policy file:

grant codeBase "file:${de.home}/-" {
  permission javax.security.auth.AuthPermission "getLoginConfiguration";
  permission javax.security.auth.AuthPermission "setLoginConfiguration";
  permission javax.security.auth.AuthPermission "createLoginContext.SunDirectoryLogin";
  permission javax.security.auth.AuthPermission "modifyPrincipals";
  permission java.lang.RuntimePermission "createClassLoader";
};

Use the grant statement shown here. The grant statement shown in Sun Java System Directory Editor 1 2005Q1 Installation and Configuration Guide is incorrect.

6397929

When deploying on Tomcat 5.5, login fails due to a missing JAAS configuration file.

To work around this issue, first create tomcat-install-path/bin/setenv.sh containing the following line:

JAVA_OPTS="-Djava.security.auth.login.config=$CATALINA_HOME/conf/jaas.conf"

Next create tomcat-install-path/conf/jaas.conf. Edit the file to contain the following lines:

SunDirectoryLogin {
 com.sun.dml.auth.SunDirectoryLoginModule required;
};

6436199

Directory Editor does not retain changes made to the Default User Form, Create. The issue occurs when the application container, where Directory Editor runs, is restarted before the changes have been validated.

To work around this limitation, do not restart the application container after restoring the configuration. Instead login, validate the Managed Directory setup under the Configure tab, save, and login again.

6441350

An application error appears after you save and continue beyond the startup page when running Directory Editor on Application Server in a locale other than English.

To work around this issue, start Application Server in the English locale on UNIX systems. On Windows systems, try restarting Application Server several times.

6456576

When you click the Help button in Directory Editor deployed in Application Server, the wrong help content is displayed.

To work around this issue, edit WEB-INF/sun-web.xml to correspond to the following, and then restart Application Server.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD 
 Sun ONE Application Server 7.0 Servlet 2.3//EN"
 "http://www.sun.com/software/sunone/appserver/dtds/sun-web-app_2_3-0.dtd">
<sun-web-app>
    <description>tomcat-test</description>
    <class-loader delegate="false"/>
</sun-web-app>

6469655

Installation of Directory Editor using the install.sh script has been seen to fail on HP-UX systems.

To work around this issue, install Directory Editor first on another system, then deploy the resulting de.war file in the web application container on your HP-UX system.

6480803

When deployed in Application Server running in a locale other than English, Directory Editor does not render English for en or en_US browser settings.

To work around this issue, issue the following commands.

# cd /var/opt/SUNWappserver/domains/domain1/applications/j2ee-modules/de/config # cp DMLMessages.properties DMLMessages_en.properties DMLMessages_en_US.properties

6487652

When logged in as a user having multi-byte characters in the user ID, you cannot edit your directory information. When you click Edit My Directory Information, you are presented with a blank page.

6488644

When you login to Directory Editor running in a locale other than English as a generic user, the Home and Change My Directory Password pages are not localized.

6489725

When you install Directory Editor in a locale other than English on Apache Tomcat on Windows, error pages are shown during configuration, save, and refresh operations.

6490590

When you install Directory Editor in a locale other than English, installer labels are not displayed properly.

To work around this issue, change to the English locale on UNIX systems before running the installer. On Windows systems, switch the locale to English using Control Panel > Regional Options before running the installer.

6492259

When accessing Directory Editor through Internet Explorer 6 running in the Spanish locale, garbage characters appear in the online help.

6493975

Directory Editor does not allow you to view multiple suffixes through the same instance.

To work around this issue, install additional instances of Directory Editor either in additional application servers or in separate domains on the same application server.