Bugs Fixed in Directory Proxy Server 6.3

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

6666615

In some cases, a client connection based on the bind DN criteria can be badly classified and an incorrect policy may be applied.

6359601

When ACIs are configured, Directory Proxy Server has been seen not to return the same results as a search directly on the LDAP data source. The Directory Proxy Server does not return any entries if the search filter contains an attribute to which access is denied.

6561078

Cannot use ldapmodify to delete a JDBC attribute if the attribute description is case-sensitive.

6490847

Established connections not kept alive.

6631652

Configuring a join-data-view with a filter join rule does not work.

6618078

When configuring a maximum connection count (max-client-connections) per client IP in the Directory Proxy Server, the number of simultaneous connections is not counted correctly.

6614510

The first request after a database stop gives no result and no error message.

6599352

The Directory Proxy Server does not start when a remote data source port is unreachable.

6560473

The Directory Proxy Server does not support object creation in SQL during a modify operation.

6597589

Adding a JDBC attribute to an entry that does not exist in JDBC does not add the entry to JDBC table.

6527869

Search doesn't work on a join view if using attributes from secondary view in the search filter.

6357160

The dpconf command does not reject new line and line feed characters in property values. Avoid using new line and line feed characters when setting property values.

6500298

When using the jvm-args flag of the dpadm command and restarting the server, you cannot successfully allocate more than 2 GB memory for the Java virtual machine.

6570523

Directory Proxy Server does not proxy the Password Modify Extended operation, which is required by the ldappasswd command to reset user passwords.