...
Limitations and Known Issues
None.
Behavior Change
...
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.
Snap Views
Type | Format | Numer of Views | Examples of Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
Input | Document |
| File Reader followed by CSV Parser. | The Distinguished name of the unit to looked for. lter to be applied to obtain the search results. |
Output | Document |
| N/A | The entry (if it exists) will be displayed with all its attributes. As of |
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 Lookup | String | Specify a unique name for the Snap. |
Distinguished name* Default Value: None | String | Specify the distinguished name of the entry 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 |
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|