If you launch the Sun ONE Directory Server 5.1 Console and create a new user or new role as inactive, the newly created user or newly created role is not inactivated. Users and roles cannot be created through the Console as inactive.
Workaround: To create an inactive user or inactive role, follow these steps:
Create the new user or new role.
Double-click the newly created user or newly created role, or select the newly created user or newly created role. Click the Properties item from the Object menu.
Click the Account tab.
Click the Inactivate button.
The newly created user or newly created role is inactivated.
If you specify a base DN that contains a space, for example, o=U.S. Government,C=US at Sun ONE Directory Server 5.1 configuration time, the resulting DN is truncated to Government,C=US. At configuration time, the DN should be typed as o=U.S.%20Government,C=US.
Workaround: To correct the base DN entry, follow these steps.
Select the top directory entry in the left side of the navigation pane of the Servers and Applications tab on the Console.
Edit the suffix in the User directory subtree field.
If you update a nonmaster directory server with password policy information, the information is not replicated to all other servers. This information includes account lockouts.
Workaround: Manage password policy information manually on each server.
If Account Lockout is effective and the user password is changed, Account Lockout remains effective.
Workaround: Reset the accountUnlockTime, passwordRetryCount, and retryCountResetTime lockout attributes to unlock the account.
If you install the Sun ONE Directory Server 5.1, start the console, initialize the directory with an LDIF file, and then back up the server, the Console reports the backup was successful. However, the backup has actually failed.
Workaround: Perform the following tasks from the Console after you initialize the database:
Stop the server.
Restart the server.
Perform the backup.
You cannot use the LDAP naming services to create automount path names that are identical, except for case results in nonunique path names. The directory server does not allow creation of entries if the naming attribute is defined with case-sensitive syntax and an entry already exists with the same name but a different case.
/home/foo and /home/Foo paths cannot coexist.
For example, if entry attr=foo,dc=mycompany,dc=com exists, the server does not allow the creation of attr=Foo,dc=mycompany,dc=com. A corollary of this problem is that when LDAP naming services are used, automount path names have to be unique, regardless of their case.
If the server is stopped during export, backup, restore or index creation, the server crashes.
Workaround: Do not stop the server during these types of operations.
The supplier's certificate is self-signed.
The supplier's certificate is only capable of behaving as an SSL server certificate that is unable to play the role of the client during an SSL handshake.