LDAP integration issue

334 views
Skip to first unread message

evlacan

unread,
Nov 4, 2010, 12:49:33 PM11/4/10
to Repo and Gerrit Discussion
Hi,

I have hard time making Gerrit integration work with our company
central LDAP server. This is the error I get:

LDAP: error code 11 - Administrative Limit Exceeded

According to this error there is a search limitation but this is the
maximum I can get. Note: this user has extensive LDAP browsing rights.

The intriguing part is that I can authenticate using the same LDAP
server and the same user name with other applications, such as JBoss
for example. The only difference here is that in JBoss I can add
indexes on the fields I'm searching trough and in this way I can find
the user I need without reaching the limit.

Using the same approach with Gerrit I get this error:

LDAP: error code 34 - Invalid DN syntax

I wonder if this is a limitation with Gerrit and if there is any
workaround that I could use instead?
Any advise and suggestion is welcome.

Thanks.

Arunciks

unread,
Nov 4, 2010, 2:40:06 PM11/4/10
to Repo and Gerrit Discussion
I got it working fine with the Active directory:
Make sure the correct branch is selected in the settings, maybe thats
an issue.

My LDAP settings in Gerrit:

[ldap]
server = ldap://10.0.0.2
username = DOMAIN\\admin
accountBase = OU=Desktops,OU=User AD
Policies,DC=xxx,DC=xx,DC=edu
groupBase = OU=Desktops,OU=User AD
Policies,DC=xxx,DC=xx,DC=edu

evlacan

unread,
Nov 4, 2010, 3:47:41 PM11/4/10
to Repo and Gerrit Discussion

Thanks for your quick reply.
I've fixed the problem, it's a bit different that you describe above
because you are using Active Directory.

In my case the username was the wrong part and this is why I was
getting this Administrative Limit Exceeded error.

It supposed to be something like this:
username = uid=username,OU=users,OU=Internal,O=company
accountBase = OU=users,OU=Internal,O=company


Somewhat I was expecting that once I give the accountBase settings,
than I don't have to specify all indexes for the username.
Wrong assumption.

Happy that it works now.

Thank again.



Reply all
Reply to author
Forward
0 new messages