Input

Document

• Min: 0

• Max: 1

File Reader followed by CSV Parser. 

The distinguished name of the unit to search, the scope of the search, and the filter to be applied.

Output

Document

• Min: 0

• Max: 1

N/A

The entry (if it exists) will be displayed with all its attributes.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:

• Stop Pipeline Execution: Stops the current pipeline execution if the Snap encounters an error.

• Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

• Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Label*

Default Value: LDAP Search
Example: Search

String

Specify a unique name for the Snap.

Distinguished name*

Default Value: None
Example: cn=syed,ou=People,dc=Snaplogic,dc=com

String

Specify the distinguished name of the entry you want to modify.

Pass through

Default Value: Deselected

Checkbox

Select this checkbox to enable the Snap to pass the input data to the downstream Snap and display in the output document.

Include string representation for binary attributes

Checkbox

Select this checkbox to add a string representation of all binary attributes. When selected, the string representation of attribute values are appended to the output document, with a _str postfix.

Search scope*

Default Value: OBJECT
Example: SUBTREE

Dropdown list

Select one of the scopes for the search:

• OBJECT (within the unit)

• ONELEVEL (within the unit and its immediate children)

• SUBTREE (within the unit and all its descendants)

Filter*

Default Value: N/A
Example: (cn=s*)

String/Expression

Specify the filter to refine and return the search results.  

Attributes

Default Value: None
Example: givenName

String

Specify the attributes that the Snap must return in the output. If you do not add any attributes, the output displays all the attributes by default.

Equality:

(attribute=abc)

for example (&(objectclass=user)(displayName=Foeckeler)

Negation:NOT Filter

(!(attribute=abc))

for example (!objectClass=group)

Presence:

(attribute=*)

for example (mailNickName=*)

Absence:

(!(attribute=*))

for example (!proxyAddresses=*)

Greater than:

(attribute>=abc)

for example (mdbStorageQuota>=100000)

Less than:

(attribute<=abc)

for example (mdbStorageQuota<=100000)

Proximity:

(attribute~=abc)

for example (displayName~=Foeckeler) Caution: ~= is treated as = in ADS environments !!

Wildcards or substring:

for example (sn=F*) or (mail=*@cerrotorre.de) or (givenName=*Paul*)

When you are not using any filter, we are checking the presence.

The Snap displays the records that start with the word user in the cn field. Here, you can see a single record.

not filter

Configure the LDAP Search Snap with a not filter.

The Snap displays all the records that do not start with the word user in the cn attribute.

and not nested filter

Configure the LDAP Search Snap with a nested filter.

The Snap displays all the records that do not start with adduser but start with the word user in the cn field. The Snap displays only one such record.