ERROR [security.sync.ChainingUserRegistrySynchronizer] [main] Synchronization aborted due to error
org.alfresco.error.AlfrescoRuntimeException: 04290001 User and group import failed
at org.alfresco.repo.security.sync.ldap.LDAPUserRegistry.processQuery(LDAPUserRegistry.java:1141)
at org.alfresco.repo.security.sync.ldap.LDAPUserRegistry.access$2500(LDAPUserRegistry.java:77)
at org.alfresco.repo.security.sync.ldap.LDAPUserRegistry$PersonCollection.<init>(LDAPUserRegistry.java:1297)
….
Caused by: javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name 'o=usaurios,o=servidor-ldap,c=com'
….
ldap.synchronization.queryBatchSize
If set to a positive integer, this property indicates that RFC 2696 paged results should be used to split query results into batches of the specified size. This overcomes any size limits imposed by the LDAP server. The default value of 1000 matches the default result limitation imposed by Active Directory. If set to zero or less, paged results will not be used.
See http://www.openldap.org/doc/admin24/limits.html#Size limits and Paged Results
sizelimit is a hard limit on the total number of results irrespective of whether paged results are used.
Support for paged results is implemented and can activated by setting ldap.synchronization.queryBatchSize.
ldap.synchronization.queryBatchSize=1000
However, as I say, on OpenLDAP you are still limited by the hard limits configured for the server. The solution is to not configure a limit smaller than the total number of results you need to handle!
Content from pre 2016 and from language groups that have been closed.
Content is read-only.
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.