"LDAP: Error Code 4 - sizelimit exceeded" using ForkJoin Plugin
(Doc ID 1548108.1)
Last updated on MAY 17, 2021
Applies to:
Oracle Virtual Directory - Version 11.1.1.0 to 11.1.1.6.0Information in this document applies to any platform.
Symptoms
When using forkjoin plugin, "LDAP: error code 4 - Sizelimit Exceeded" could be returned even if the number of entries that should be returned is less than the size limit defined
Changes
Steps to reproduce the issue:
-------------------------------
1. Create two ldap adapters and one Join adapter with ForkJoin plugin
2. Execute a ldapsearch with size limit similar to:
ldapsearch -p <OVD_PORT> -D cn=orcladmin -w <PASSWORD> -z 1 -s sub -b "cn=Users,dc=<JOIN_CONTAINER>,dc=<COMPANY_NAME>,dc=com" "(&(objectclass=person)(uid=<UID>*))"
ldap_search: Sizelimit exceeded
ldap_search: additional info: [LDAP: error code 4 - Sizelimit Exceeded]
If flag -z is set to a higher value then the ldapsearch returns the correct result:
Example:
ldapsearch -p <OVD_PORT> -D cn=orcladmin -w <PASSWORD> -z 7 -s sub -b "cn=Users,dc=<JOIN_CONTAINER>,dc=<COMPANY_NAME>,dc=com" "(&(objectclass=person)(uid=<UID>*))"
vdejoindn: <adapter_name>:cn=<CN>,cn=Users,dc=<DC>,dc=<COMPANY_NAME>,dc=com
cn: <CN>
uid: <UID>
description: Testing User
orclsamaccountname:<SAMACCOUNTNAME>
sn: <SN>
mail: <EMAIL_ADDRESS>
givenname: user1
userpassword: {SSHA} <HASHED PWD>
objectclass: top
objectclass: person
objectclass: organizationalPerson
objectclass: inetOrgPerson
objectclass: orclUser
objectclass: orclUserV2
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |