Ldap Error Code 11 - Administrative Limit Exceeded Jenkins
- 15th for workshops, presentations and all things Jenkins Learn more Export Tools JenkinsJENKINS-3460LDAP authentication doesn't work starting from build 1.286Log In ExportXMLWordPrintable Details Type: Bug Status: Closed Priority: Major Resolution: Postponed Component/s: other Labels: None Environment: Platform: All, OS: All Similar Issues: Show Description LDAP authentication doesn't work starting from build 1.286. Error is the following org.acegisecurity.AuthenticationServiceException: LdapCallback;[LDAP: error code 11 - Administrative Limit Exceeded]; nested exception is javax.naming.LimitExceededException: [LDAP: error code 11 - Administrative Limit Exceeded]; remaining name ''; nested exception is org.acegisecurity.ldap.LdapDataAccessException: LdapCallback; This bug appeared after an update from version 1.286 to version 1.297. AttachmentsActivity All Comments History Activity Ascending order - Click to sort in descending order 5 older comments Hide Permalink Alan Harder added a comment - 2009/Dec/22 12:25 PM - edited The fix between those versions (1.289 to be exact) was adding back the LDAP group query that was inadvertently removed in 1.280. Here is the change: --- war/resources/WEB-INF/security/LDAPBindSecurityRealm.groovy (revision 15955) +++ war/resources/WEB-INF/security/LDAPBindSecurityRealm.groovy (revision 16034) @@ -64,4 +64,5 @@ authoritiesPopulator(AuthoritiesPopulatorImpl, initialDirContextFactory, Util.fixNull(instance.groupSearchBase)) { // see DefaultLdapAuthoritiesPopulator for other possible configurations searchSubtree = true; + groupSearchFilter = "(| (member={0}) (uniqueMember={0}) (memberUid={1}))"; } Perhaps the group query is what causes you to exceed some "Administrative Limit"? Maybe customize your LDAPBindSecurityRealm.groovy file, and either remove that line or change it to just the query you need for your LDAP, such as: groupSearchFilter = "(uniqueMember= {0} )"; Let us know if this helps, or if we should just close this issue..
- 15th for workshops, presentations and all things Jenkins Learn more Export Tools JenkinsJENKINS-3460LDAP authentication doesn't work starting from build 1.286Log In ExportXMLWordPrintable Details Type: Bug Status: Closed Priority: Major Resolution: Postponed Component/s: other Labels: None Environment: Platform: All, OS: All Similar Issues: Show Description LDAP authentication doesn't work starting from build 1.286. Error is the following org.acegisecurity.AuthenticationServiceException: LdapCallback;[LDAP: error code 11 - Administrative Limit Exceeded]; nested exception is javax.naming.LimitExceededException: [LDAP: error code 11 - Administrative Limit Exceeded]; https://issues.jenkins-ci.org/browse/JENKINS-3460 remaining name ''; nested exception is org.acegisecurity.ldap.LdapDataAccessException: LdapCallback; This bug appeared after an update from version 1.286 to version 1.297. AttachmentsActivity All Comments History Activity Ascending order - Click to sort in descending order nicusorb created issue - 2009/Apr/08 4:31 AM Hide Permalink mdonohue added a comment - 2009/May/10 8:01 PM LDAP is pretty widely https://issues.jenkins-ci.org/browse/JENKINS-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel used with Hudson, and I haven't seen any traffic on the users list about this issue. Are you still having a problem? Show mdonohue added a comment - 2009/May/10 8:01 PM LDAP is pretty widely used with Hudson, and I haven't seen any traffic on the users list about this issue. Are you still having a problem? Hide Permalink nicusorb added a comment - 2009/May/27 2:34 AM Yes, I'm still having the problem. The problem appeared after an update to Hudson. Nothing was changed in my LDAP configuration. Show nicusorb added a comment - 2009/May/27 2:34 AM Yes, I'm still having the problem. The problem appeared after an update to Hudson. Nothing was changed in my LDAP configuration. Hide Permalink Andrea Barbieri added a comment - 2009/May/27 4:40 AM Hello, I'm using the LDAP authentication quite successfully (just hitting issue 2489 practically on a daily basis) and have been using it since 1.275. I do make use of
map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor. Announcement Announcement Module Collapse No announcement yet. [beginner] Can't http://forum.spring.io/forum/spring-projects/data/ldap/48926-beginner-can-t-get-ldap-to-work-limitexceededexception get LDAP to work (LimitExceededException) Page Title Module Move Remove Collapse X Conversation http://serverfault.com/questions/286130/jenkins-hudson-ldap-group-lookup-does-not-work Detail Module Collapse Posts Latest Activity Search Forums Page of 1 Filter Time All Time Today Last Week Last Month Show All Discussions only Photos only Videos only Links only Polls only Filtered by: Clear All new posts Pierrre Junior Member Join Date: Jul 2008 Posts: 15 #1 [beginner] Can't ldap error get LDAP to work (LimitExceededException) Jul 11th, 2008, 07:36 AM Hello there! Since it's my first message, I'm gonna introduce myself a bit. I've been using AppFuse for a project, which comes with Spring framework. I've been asked to be able to list a LDAP directory and display a table resulting from this request. I know how to do that with a ldap error code Database using Hibernate (included in AppFuse, too), but I didn't really know how to deal with LDAP directories, until I hear about spring-ldap. I read some docs about it, and it seems to be exactly what I am looking for... but I can't get it work! So I have a JSP that should display a table containing the information I want from the LDAP directory. This JSP is connected by a class Action which calls the getUtilisateurs() method, which is the same as findAll() in the spring-ldap tutorials I've seen so far. This method is implemented in a class called UtilisateurDaoLdap.java like this: Code: public List getUtilisateurs() { EqualsFilter filter = new EqualsFilter("objectclass", "person"); return ldapTemplate.search(DistinguishedName.EMPTY_PATH, filter .encode(), getContextMapper()); } When this method is called, an exception is thrown: Code: org.springframework.ldap.LimitExceededException: [LDAP: error code 3 - Timelimit Exceeded]; nested exception is javax.naming.TimeLimitExceededException: [LDAP: error code 3 - Timelimit Exceeded]; remaining name '/' Caused by: javax.naming.TimeLimitExceededException: [LDAP: error code 3 - Timelimit Exceeded]; remaining name '/' But normally, all the information needed to connect to the LDAP directory is set in a ApplicationContext-*.xml Code: