LDAP errors - Logs of no help

Hi - I've enabled logging, to try and debug my LDAP sync problems. Here is what the log shows.

[2010-10-26 17:14:34,441]   INFO -     jetbrains.buildServer.LDAP - ------ Sync with LDAP users started ------
[2010-10-26 17:14:34,446]   WARN -     jetbrains.buildServer.LDAP - Fatal error while LDAP users synchronization: Invalid DN syntax ([LDAP: error code 34 - invalid DN]; nested exception is javax.naming.InvalidNameException: [LDAP: error code 34 - invalid DN])
[2010-10-26 17:14:34,446]   INFO -     jetbrains.buildServer.LDAP - Last syncronization statistics: created users=0, updated users=0, removed users=0, users in ldap=0, matched users=0, duration=5ms, errors=[Fatal error while LDAP users synchronization: Invalid DN syntax ([LDAP: error code 34 - invalid DN]; nested exception is javax.naming.InvalidNameException: [LDAP: error code 34 - invalid DN])]

Is this what you would expect to see? Without giving me the DN that it is attempting to use, I can go no further with the debugging - it just tells me what I already know from the admin section. Could this be enhanced please?

Ben

3 comments

So I'm not in such a bad mood today. Spent the whole day trying to find out why the syntax is not correct. Would someone please be able to look at the ldap-config-properties file attached and tell me which bit I need to correct? It has been a long time since I've used LDAP, and my path to a user, copied out of an LDAP browser is uid=myname,cn=users,dc=beer,dc=wine,dc=vodka

Thanks

Ben



Attachment(s):
bt-ldap-config-properties.zip
0

Hi Ben,

Are you able to login to TeamCity with LDAP?
Please check your "java.naming.security.principal" property, there should be full DN of the user, not just username.

Also error code 34 usually indicates wrong "base" setting ("teamcity.users.base" or "teamcity.groups.base"). Can you try to put empty value there (just for the test)?


---
Maxim

0

Hi

Magic! Setting the "java.naming.security.principal" property to the full DN of the user fixed everything.

Yes - login always continued to work fine for existing and new users. The base setting was also correct.

Thank you very much, massive help!

Ben

0

Please sign in to leave a comment.