Environment
We had a customer who was unable to locate new users while
browsing the containers to associate them.
Discovered the GroupWise search request uses sizelimit:1000.
This particular container had over 1000 user objects, and anything
new over 1000 would not be displayed.
Example of LDAP search request:
1241401088 LDAP: [2016/10/04 11:18:31.542]
(151.155.215.39:40374)(0x0002:0x63) Search request:
base: "ou=Users,o=novell"
scope:1 dereference:3
sizelimit:1000 timelimit:0 attrsonly:0
filter:
"(|(objectclass=person)(objectclass=container)(objectclass=domain)(objectclass=organization)(objectclass=organizationalUnit)(obje
ctclass=country)(objectclass=locality))"
attribute: "cn"
attribute: "objectClass"
attribute: "o"
attribute: "ou"
attribute: "dc"
attribute: "c"
attribute: "l"
attribute: "objectClass"
attribute:
"javaSerializedData"
attribute: "javaClassName"
attribute: "javaFactory"
attribute: "javaCodeBase"
attribute:
"javaReferenceAddress"
attribute: "javaClassNames"
attribute:
"javaRemoteLocation"
using the '-z 1000' switch duplicated these results with a
manual ldapsearch
Situation
This has been reported to engineering.
As a workaround step, we had to manually enter in the users
full LDAP context to associate.