This topic needs further documentation to make it awesome. If you have experience with this transformation step, we encourage you to update this topic. More information can be found in JIRA case DOC-2115.
Limitation documented in PDI-17823: If you have a transformation with multiple LDAT Input or LDAP Output steps (talking to two different LDAP servers with different configurations) or simultaneous transformations with differently configured LDAP steps, one transformation's configuration will step all over the other transformation's configuration.
Description
The LDAP Input step allows you to read information like users, roles and other data from an LDAP server. The following sections describe the available options for the LDAP input step.
General Tab
Option | Description |
---|---|
Step name |
Host | Host on which the LDAP server is running |
Port | Port number on which the LDAP server is running |
Use Authentication |
Username | |
Password |
Test connection button |
Preview rows button |
Search Tab
Option | Description |
---|---|
Search base | Base LDAP node to search the LDAP contents |
Filter String | LDAP filter to search the customized contents, in the current stage only "single filter format" is supported like. |
Content
Option | Description |
---|---|
Include rownum in output? |
Rownum fieldname |
Limit |
Fields
Option | Description |
---|---|
Name |
Column |
Type |
Format |
Length |
Precision |
Currency |
Decimal |
Group |
Trim type |
Repeat | If LDAP returns no value for an attribute, use the value from the previous row |