|
If you were logged in you would be able to see more operations.
|
 Google issue summary
|
|
|
|
Environment:
|
Nuxeo-5.1-M1
|
|
Issue Links:
|
Dependency
|
|
|
|
This issue is required by:
|
|
|
|
|
|
|
|
|
We are using the LDAP Directory to access our enterprise LDAP. The problem is that there are more than 15000 entries in it. The LDAPSession object doesn't include a limitation in the number of entries it should return.
There should be a parameter in the LDAPDirectoryDescriptor to limit the maximum number of item to return. I made a few tests to see if it works. The problem is that the comportment of the application when the maximum number is reached should be decided : return the firsts results or return only an empty list.
Then the comportment can also be changed in the UserManager when it receive an SizeExceed exception...
Do we have to developp our UserManager Implementation or LDAPDirectory that derives from the Nuxeo one, or will there be updates on it ?
|
|
Description
|
We are using the LDAP Directory to access our enterprise LDAP. The problem is that there are more than 15000 entries in it. The LDAPSession object doesn't include a limitation in the number of entries it should return.
There should be a parameter in the LDAPDirectoryDescriptor to limit the maximum number of item to return. I made a few tests to see if it works. The problem is that the comportment of the application when the maximum number is reached should be decided : return the firsts results or return only an empty list.
Then the comportment can also be changed in the UserManager when it receive an SizeExceed exception...
Do we have to developp our UserManager Implementation or LDAPDirectory that derives from the Nuxeo one, or will there be updates on it ? |
Show » |
|
Improvement
Critical
Big LDAP Tree is unbrowseable
So you won't have to make your own directory.
For now, if you want to test without the volume problem, just add some filters in the LDAP configuration.