-
Bug
-
Resolution: Fixed
-
Low
-
None
-
2.0.3
-
None
-
Documentation bug (N/A)
The documentation at http://confluence.atlassian.com/display/CROWDKB/_Error+when+browsing+users,+groups+or+roles+for+Active+Directory indicates that the naming exception can be solved by using a FQDN for the AD server. I was using an IP address for my AD server and got this error (and continued to get it when I changed to an IP address).
The error went away for me when I retyped the password for the AD user I was using to log in – I either got it wrong the first time I typed it in, or it had wound up blank. I think that page should be updated to indicate that that's another possible problem if you see that error.
Cheers.
[CWD-1785] Documentation answer for LDAP error is wrong
David O'Flynn [Atlassian]
added a comment - I've updated the KB entry. We've looked into providing an error translator, but it's not quite made the roadmap yet.
David O'Flynn [Atlassian]
added a comment - I've updated the KB entry. We've looked into providing an error translator, but it's not quite made the roadmap yet. 
Andrew Moise
added a comment - Actually, on working with Crowd a bit more, I think the answer to this is to update the software to print a real error message instead of a stack trace. Printing a stack trace (which apparently can be caused by multiple kinds of misconfigurations) and then asking people to search for what the stack trace means seems not as good as just telling people what the error may be (even if there are multiple possibilities for the error).
E.g. One message to display might be "Could not connect to the LDAP server; possibly the host indicated is not correct, the LDAP server is not running on that host, or the password is blank or incorrect."
Andrew Moise
added a comment - Actually, on working with Crowd a bit more, I think the answer to this is to update the software to print a real error message instead of a stack trace. Printing a stack trace (which apparently can be caused by multiple kinds of misconfigurations) and then asking people to search for what the stack trace means seems not as good as just telling people what the error may be (even if there are multiple possibilities for the error).
E.g. One message to display might be "Could not connect to the LDAP server; possibly the host indicated is not correct, the LDAP server is not running on that host, or the password is blank or incorrect." 
Excellent, thanks!