In this article
You can use the LDAP Search Snap to perform an LDAP search based on the Distinguished Name (DN) with a specific filter.
The LDAP Search is a Read-type Snap.
None.
Works in Ultra Task Pipelines.
None.
As of 432patches19873
Snap Pack version, any LDAP entry attribute that contains binary data will be displayed as a byte array (Base64 encoded) instead of a string in the output.
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
| 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 |
| 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:
Learn more about Error handling in Pipelines. |
|
Field Name | Field Type | Description |
---|---|---|
Label* Default Value: LDAP Search | String | Specify a unique name for the Snap. |
Distinguished name* Default Value: None | 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. In certain scenarios, the Snap might be unable to process the entire input due to limitations imposed by the endpoint's API. In such cases, we recommend that you select the Pass through checkbox to ensure that the unprocessed input is not lost. You can process the remaining input data using more of the same Snap in the pipeline. Alternatively, you can also write the original data into a separate file using a combination of the Mapper Snap and the File Writer Snap. In certain scenarios, the Snap might be unable to process the entire input due to limitations imposed by the endpoint's API. In such cases, we recommend that you select the Pass through checkbox to ensure that the unprocessed input is not lost. You can process the remaining input data using more of the same Snap in the pipeline. Alternatively, you can also write the original data into a separate file using a combination of the Mapper Snap and the File Writer Snap. |
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 |
Search scope* Default Value: OBJECT | Dropdown list | Select one of the scopes for the search:
|
Filter* Default Value: N/A | String/Expression | Specify the filter to refine and return the search results.
|
Attributes
| 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. |
Filter | Syntax for the filter |
---|---|
|
for example |
|
for example |
|
for example |
|
for example |
|
for example |
|
for example |
|
for example |
| for example |
and
not
filters The example pipeline demonstrates how to use and
not
filters to fetch records based on the specified common name (cn).
Step1: Configure the LDAP Search Snap with the Distinguished name as follows:
Step 2: Configure specific filters to obtain the required results, as shown below.
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. | |
| |
Configure the LDAP Search Snap with a | The Snap displays all the records that do not start with the word user in the cn attribute. |
| |
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. |