The LDAP reader connector reads data from LDAP server through Lightweight Directory Access Protocol (LDAP). See the Configuration section for a description of each option.
Configuration
LDAP Connection (ver. 1.1.0)
Hostname
The URL of the LDAP server. Define LDAP server in IP address format or dotted format (port can be also included).
Example
- ldap.ups.local
- ldap.ups.local:389
- 192.168.0.1
- 192.168.0.1:389
Authentication Type
Supported authentication types
- Basic - Uses standard LDAP authentication without encrypted communication. Suitable for development or internal environments where encryption is not required.
- Secured - Uses LDAPS (LDAP over SSL/TLS) for encrypted communication. Recommended for production use.
Requirement for secured authentication
To use the Secured authentication type, the LDAP server must have a certificate issued by a trusted certificate authority (CA). Alternatively, a remote agent must be used on a server where the appropriate certificate is already installed and trusted.
BaseDN
Base DN is the starting point of LDAP directory.
It is defined by attributes
- o - organization
- ou - organizational unit
- dc - domain component
- uid - user ID
- cn - common name ...
dc=example,dc=com
Username
Defines the login name that is used for connection authentication.
cn=read-only-admin,dc=example,dc=com
Password
Define the password that is used to authenticate the connection.
Filter
Defines the criteria used to identify entries in search request. Filters are a key element in defining the criteria used to identify entries in search requests.
(objectClass=inetOrgPerson)
For more examples of connection strings, see official documentation.
LDAP Attributes (ver. 1.0.0)
Result Path
Defines the LDAP Attributes that will be selected from LDAP server entries.
Input & Output Schema
Input
Data schema is optional
The connector does not expect a specific schema. The required data structure can be achieved by correct configuration. Although the selected connector doesn't require a schema generally, the individual integration task step may need to match the output data structure of the preceding task step and use a data schema selected from the repository or create a new input schema.
Output
JSON (ver. 1.0.0)
| Column | Data type | Allow null | Description |
|---|---|---|---|
| JSON | JSON | No | Input/Output in JSON format |
Example
LDAP Attribute configuration:
{
"Attributes":[
{
"Value":"uid"
},
{
"Value":"cn"
},
{
"Value":"adspath"
}]
}
[
{
"uid":"newton",
"adspath":"LDAP://ldap.forumsys.com/uid=newton,dc=example,dc=com",
"cn":"Isaac Newton"
},
{
"uid":"einstein",
"adspath":"LDAP://ldap.forumsys.com/uid=einstein,dc=example,dc=com",
"cn":"Albert Einstein"
}
]
Release notes
3.1.0
- Added support for communication with LDAP servers using LDAPS.
3.0.3
- Fixed shared nuget package versions.
3.0.2
- Fixed right processing of nullable properties.