Red Hat DIRECTORY SERVER 8.1 - RELEASE NOTES Release Note page 16

Red Hat Directory Server 8.1 Release Notes
Bug Number Description
the default value as 20000000 bytes, not the auto size. And, since auto cache
sizing takes priority over manually assigning the cache size, whatever was set in
the Directory Server Console was ignored.
The Directory Server Console has a new checkbox to enable or disable auto cache
sizing. If auto cache sizing is enabled, the value set for the cache size is ignored.
245894 Occasionally, the Directory Server's ns-slapd could shut down successfully,
but its .pid file wasn't removed. If there was an existing .pid file for a server
instance, then the server could not restart, even if it wasn't running.
381361 Some cn changes on Directory Server were not synced over to Active Directory.
387851 The Directory Server would allocate as much memory as a client suggested for a
SASL operation, without any other limits being imposed. This can be restricted now
in Directory Server 8.1 through the new nsslapd-maxsasliosize configuration
attribute, which sets a limit on the size of incoming SASL packets.
400341 If a user was logged in as the Directory Manager and tried to change the admin
user's password in the Administration Server's Console, the server would try to
change the Directory Manager's password instead.
400361 Changing the admin user's password in the Administration Server Console closed
the connection to the Console immediately when the change was saved.
426139 When a non-privileged user logged into a console and attempted to open a
configuration tab, the console would throw Java exceptions to standard output and
open error dialogs.
426421 The Windows version of the Directory Server Console looked for its NSS libraries in
the wrong location.
426435 If a CRL was located in the /usr/lib/dirsrv/slapd-instance_name
directory, it could not be added to the CRL tab of the Directory Server Console's
Certificate Wizard. If the CRL was located anywhere else, it could be loaded
through the Certificate Wizard just fine.
428232 Performing a rename operation failed if the DN was only different in case (such as
cn=john smith to cn=John Smith) or where the new DN was identical to the
old DN.
428929 The Directory Server was caching the values of attributes with DirectoryString
formats. For example, if a an attribute was added with a value in all capital letters,
and then the value was deleted and replaced with all lower case letters, sometimes
the Directory Server would return the correct lower-case value, and sometimes it
would return the previous upper-case value. This happened because replication
doesn't delete attribute values; it stores them with state information. When the
attribute was re-added, the old attribute was resurrected with updated state
information and, since DirectoryString is case-insensitive, the old value looked
identical to the new value.
429514 The date and time fields were incorrectly parsed and displayed in the
Administration Server Console.
429631 If a virtual subtree was used to configure synchronization, the Directory Server
crashed.
429793 Consumer initialization would crash the consumer server or the process would
429799 hang endlessly if there was an entry with a very large attribute.
16