How to Build a Search Filter in LDAP Query

...batchSize:-1
)
)

2. ldapsearch(
config:{
scsExternalSystemKey:"ldap.local",
usePerUserCredentials:false,
url:"ldap://myhostname:389",
baseDN: "dc=appian"
},
searchFilter:"(&(ObjectClass=inetOrgPerson)(uid=user.1)(memberof=CN=development,OU=hr,DC=appian))",
attributes:{},
pagingInfo:a!pagingInfo(
startIndex:1,
batchSize:-1
)
)

3. ldapsearch(
config:{
scsExternalSystemKey:"ldap.local",
usePerUserCredentials:false,
url:"ldap://myhostname:389",
baseDN: "dc=appian,ou=hr"
},
searchFilter:"(&(ObjectClass=inetOrgPerson)(uid=user.1)(memberof=CN=development,DC=appian))",
attributes:{},
pagingInfo:a!pagingInfo(
startIndex:1,
batchSize:-1
)
)

Note:
1. I know that 'LDAP' under 'Authentication' section in Admin Console might be an option but my prime intention is to make fn!ldapsearch() (of LDAP Tools plugin) work.
2. Appian is able to talk to LDAP server successfully as I can see results when the search fil...

...ter is configured such as "(&(ObjectClass=inetOrgPerson)(uid=user.1))". So there isn't any problem with integration.
3. Nothing is being recorded in the logs as the functionality isn't failing technically.
4. I have made a search through the posts made in the forum earlier on the LDAP, so it would be grateful if the links to earlier posts aren't made.

Thanks in advance.

Please find attached screenshots that represents the LDAP structure.

memberOf is an attribute on the user object, I do not see it in your directory model. AD has that attribute by default, other directory vendors may not. I am not sure you will be able to write a correct filter query without changing the plugin itself.

@Mike Cichy Thanks for the input. I will try to see what can be done if the LDAP vendor I made use of lacks memberOf. If this is the case, can't I simply change my search filter in such a way that it makes use of the new attribute (in the LDAP vendor I am making use of) that is equivalent to memberOf in AD?

There could be something there but based on my experience, the synch needs to be changed since you are no longer searching for users based on a query. You are accessing a group and retrieving its members. This will be a different API call altogether.
The approach is partly explained here: stackoverflow.com/.../ldap-group-has-members-but-the-members-dont-have-the-memberof-attribute

Just to give an update, I was able to resolve the issue. The LDAP vendor I have used is making use of a attribute by name 'isMemberOf' which is equal to 'memberOf' attribute in AD. Additionally inclusion of OU attribute in the searchFilter has blocked the results.

Following expression is able to return me the results I have desired for:
fn!ldapsearch(
config:{
scsExternalSystemKey:"ldap.local",
usePerUserCredentials:false,
url:"ldap://myhostname:389",
baseDN: "dc=appian,ou=hr"
},
searchFilter:"(&(ObjectClass=inetOrgPerson)(uid=user.1)(isMemberOf=cn=development,dc=appian))",
attributes:{},
pagingInfo:a!pagingInfo(
startIndex:1,
batchSize:-1
)
)

@mike.cichy Thanks for the inputs.

@sikhivahans, May I know how to setup Third-Party Credentials store for LDAP Search plug-in, I am using username(AD ID / sAMAccount) / password (AD password). Do I need to use complete DN for user name?

@saravanana Please find attached the document that demonstrates what and how I did.

214261.docx

Using complete DN as username is working for third party credentials store