Active Directory Search
In this article
Overview
You can use this Snap to search for items in Active Directory. It also provides options to select the scope and provide filter attributes to effectively return search results.
The attributes of table are populated in the suggestions list based on the existing distinguished name in Active Directory. The table consists of all the fields that can be used as filter attributes to perform search and effectively return the results.
Snap Type
The Active Directory Search Snap is a Read-type Snap that reads the matched entries based on the filter criteria.
Prerequisites
A valid Active Directory Basic Auth account.
Existing distinguished name.
Support for Ultra Pipelines
Works in Ultra Pipelines.
Behavior change
Previously the Page Size field worked similar to the Limit field, that is, it set the limit on fetching records instead of fetching all the records.
The Active Directory Search Snap output now displays the number of records that you specify in the Limit field under Settings. If your Pipelines use the Snap with the Page Size field, they may fail to execute if the downstream Snap expects the same count. To retrieve all the records, configure the Snap with default settings, that is, Limit: 0 and Page Size: 1000.
Snap Views
Type | Format | Number of views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
| File reader followed by any file Parser followed by Structure. | Existing distinguished name, Filter attributes (Filter keys, Filter values). |
Output | Document |
| Any file Formatter followed by File Writer. | The output data and the searched entries based on the specifed existing distinguished name. |
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 while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab. The available options are:
Learn more about Error handling in Pipelines. |
Limitations and Known Issues
None.
Snap Settings
Asterisk (*): Indicates a mandatory field.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon (): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon (): Indicates that you can add fields in the field set.
Remove icon (): Indicates that you can remove fields from the field set.
Field | Field Type | Description |
Label* Default Value: Search | String | Specify a unique name for the Snap. |
Existing distinguished name* Default Value: None | String/Expression | Specify the LDAP API references an LDAP object by its distinguished name (DN). A DN is a sequence of relative distinguished names (RDN) connected by commas. An RDN is an attribute with an associated value in the form attribute=value, normally expressed in a UTF-8 string format. The typical RDN attribute types include: DC = domainComponent, CN = commonName, OU = organizationalUnitName,O = organizationName, STREET = streetAddress, L = localityName,ST = stateOrProvinceName, C = countryName, UID = userid. A distinguished name for an LDAP entry can be represented as: CN=AbcUser,CN=Users,DC=server,DC=company,DC=com. In this example, to refer to the entire user list, you can remove the initial attribute, CN=AbcUser. This field is applicable only to existing users. If the user does not exist, create an entry using the Create Entry Snap first. You can also use special characters in the distinguished name. Learn more about Using Special Characters in Distinguished Name. |
Page size* Default Value: 1000
| Integer |