LDAP type data source
An LDAP data source is automatically created when you configure your instance to integrate with LDAP.
Processing a large LDAP request without paging
When an LDAP server does not support paging, a large request is automatically broken into multiple smaller requests.
This process is known as "nibbling" the LDAP request. The large request is broken into multiple smaller requests based on the value of the Query field in the LDAP OU definition. This field should specify a unique value such as email address or user ID.
For example, the following LDAP query might return more than 1000 records.
(&(objectclass=user)(sn=*))
In this example, the LDAP server Query field is
preferredIdentity. The instance then splits the large request into
multiple smaller requests, grouping records based on the
preferredIdentity
value.
(&((&((preferredIdentity>=0)(preferredIdentity<=1))))((&(objectclass=user)(sn=*))))
(&((&((preferredIdentity>=1)(preferredIdentity<=2))))((&(objectclass=user)(sn=*))))
(&((&((preferredIdentity>=2)(preferredIdentity<=3))))((&(objectclass=user)(sn=*))))
. . .
(&((&((preferredIdentity>=9)(preferredIdentity<=a))))((&(objectclass=user)(sn=*))))
(&((&((preferredIdentity>=a)(preferredIdentity<=b))))((&(objectclass=user)(sn=*))))
(&((&((preferredIdentity>=b)(preferredIdentity<=c))))((&(objectclass=user)(sn=*))))