This chapter covers the status of key issues and limitations for OpenDJ and OpenDJ SDK . For details and information on other issues, see the OpenDJ issue tracker.

The following important bugs were fixed in this release. TODO

Release has the following limitations, none of which are new since . OpenDJ directory server provides full LDAP v3 support, except for alias dereferencing, and limited support for LDAPv2. When you configure account lockout as part of password policy, OpenDJ locks an account after the specified number of consecutive authentication failures. Account lockout is not transactional across a replication topology, however. Global account lockout occurs as soon as the authentication failure times have been replicated. OpenDJ is not fully integrated with Microsoft Windows, yet OpenDJ directory server can be run as a service, and thus displayed in the Windows Services Control Panel. OpenDJ replication is designed to permit an unlimited number of replication servers in your topology. Project testing has, however, focused only on topologies of up to eight replication servers. On Niagara systems such as T2000, hardware SSL crypto acceleration runs more slowly than software crypto acceleration. To work around this issue take the following actions. Add more request handlers to LDAP (for TLS) and LDAPS (for SSL) connection handlers. Disable hardware acceleration for server's JVM by removing the SunPKCS11 security provider from jre/lib/security/java.security.

When deploying for production, make sure that you follow the installation instructions on allowing OpenDJ to use at least 64K (65536) file descriptors, and on tuning the JVM appropriately. The following important issues remained open at the time this release became available. TODO