Taken from the user forums:

there seems to be an important bug in Sun One DS connector (I'm using Crowd v1.0.6).

I want to authenticate and provision my JIRA users on an LDAP directory. I have done all the integration between Jira and Crowd and it works very well when using openLDAP as the repository for JIRA users (both LDAP authentication and Single Sign-On).

It does not work on Sun One Directory Server because the connector always uses the password of the technical account that is configured in the console instead of using the password that is provided by the user. For instance, let's say you have configured the connector with "cn=Directory Manager" and "adminpassword" as the password for this user. If a user like "cn=bruno, dc=mycompany" owns a password different than "adminpassword" he won't be able to log in. If you don't indicate any technical account in the configuration panel, the connector always performs an anonymous bind when you try to login. It should first perform an anonymous bind to search the DN of the user trying to log in and then bind with this very DN and the provided password...