You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 14, 2024. It is now read-only.
On upgrading ldapjs from version '2.3.3' to '3.0.2', 2.3.3 was able to get all values of the member attribute when we changed range minimum and maximum but with version 3.0.2 the client.search method started failing with error: "Error: attribute must be a valid string".
The code snippet of the options sent in the ldapjs client.search method has been attached below.
let opts = {
filter: cn=${cnValue},
scope: 'sub',
attributes: [ 'member;range=0-1499'],
timeLimit: 30
}
Is there some way we can send the range in attributes with the new ldapjs version or an alternate way to get all the data of member attribute at once (There are >2000 members for one object)?
The text was updated successfully, but these errors were encountered:
All the members were earlier being received by sending attributes in the form "member;range=0-1499", "member;range=1500-max' and so on. But with version "3.0.2", it is giving error. Is there some alternate way of getting member data for items having member>1500?
The problem is not resolved in the, issue tagged as duplicate.
On upgrading ldapjs from version '2.3.3' to '3.0.2', 2.3.3 was able to get all values of the member attribute when we changed range minimum and maximum but with version 3.0.2 the client.search method started failing with error: "Error: attribute must be a valid string".
The code snippet of the options sent in the ldapjs client.search method has been attached below.
let opts = {
filter:
cn=${cnValue}
,scope: 'sub',
attributes: [ 'member;range=0-1499'],
timeLimit: 30
}
Is there some way we can send the range in attributes with the new ldapjs version or an alternate way to get all the data of member attribute at once (There are >2000 members for one object)?
The text was updated successfully, but these errors were encountered: