Status

FunctionalityStable
Support statusSupported
Support provided byEvolveum
OriginEvolveum
Target systemsStandard LDAP servers (LDAPv3)

This is the recommended connector to connect midPoint with the LDAP servers.

Description

Connector for standard LDAPv3 directory servers.

This is an LDAP connector completely rewritten from scratch in 2015. It is using Apache Directory API and it is designed and built to work with recent ConnId versions and to take all the advantages of that. This is the supported and recommended LDAP and AD connector for midPoint. The old LDAP and AD connectors are now deprecated and they are no longer supported.


Protocol

LDAP or LDAPS

Framework

ConnId 1.5.x

Bundle name

com.evolveum.polygon.connector-ldap

Connector name

com.evolveum.polygon.connector.ldap.LdapConnector

Source codehttps://github.com/Evolveum/connector-ldap

Capabilities and Features

SchemaYESDetermined from standard LDAP schema.

Provisioning

YES


Live Synchronization

YES

For LDAP servers that support Sun-style changelog (Retro ChangeLog) or modifyTimestamp.

There is a contributed code for OpenLDAP synchronization. However, this is not included in "bundled" support.

Password

YES

It is assumed that the server will hash the password and store it securely. Support for connector-side hashing is limited.

Activation

PARTIAL

No activation for generic LDAP as there is not LDAP standard for that. This can be simulated in midPoint.

Filtering changes


currently limited

Paging support

YES

Simple Paged Results and VLV

Native attribute namesYES

Use ri:dn instead of icfs:name

Use ri:entryUUID instead of icfs:uid

History

This is an LDAP connector completely rewritten from scratch during 2015. It was significantly improved in following years. Currently the LDAP connector is perfectly stable and tested in many deployments. It can be used with a variety o LDAP servers, including exotic and obsolete systems.

Versions

Version

Origin

Binary

Sources

Build Date

Framework versionBundled with midPoint

Description

1.4.1.23

Polygon

download jar

GitHub

August 2015



Experimental version.

1.4.2.0Polygon

download jar

GitHub

December 20151.4.2.0

LDAP stable, AD experimental

1.4.2.14Polygon

download jar

GitHub

April 20161.4.2.143.3.1Stable.
1.4.2.15Polygon

download jar

GitHub

April 20161.4.2.14
Stable.
1.4.2.16Polygondownload jarGitHubJune 20161.4.2.14
Fixes timeout errors and resource leaks during AD connector resets.
1.4.2.17Polygondownload jarGitHubJune 20161.4.2.143.4Minor fixes.
1.4.2.18Polygondownload jarGitHubSeptember 20161.4.2.143.4.1Minor improvements.
1.4.2.19Polygondownload jarGitHubOctober 20161.4.2.18
Minor improvements.
1.4.3Polygondownload jarGitHubDecember 20161.4.2.183.5Minor improvements.
1.4.4Polygondownload jarGitHubApril 20171.4.2.183.5.1CredSSP and Exchange powershell support, bugfixes, minor improvements.
1.4.5Polygondownload jarGitHub3rd July 20171.4.2.183.6Powershell bugfixes, minor improvements.
1.5Polygondownload jarGitHub4th October 20171.4.2.183.6.1More powershell execution alternatives and improvements, alternative auxiliary object class detection, explicit object class filter, configurable timestamp presentation, better error messages.
1.5.1Polygondownload jarGitHub11th December 20171.4.2.183.7, 3.7.1Release coupled with AD connector.
1.6Polygondownload jarGitHub4th May 20181.4.2.183.7.2, 3.8Release coupled with AD connector.
1.6.1Polygondownload jarGitHub17th April 20191.4.2.18TBDFix of security vulnerability: missing check of certificate validity.
2.0Polygondownload jarGitHub7th November 20181.5.0.03.9Native timestamp support. Support for delta-based updates. Additional search filter support.
2.1Polygondownload jarGitHub17th April 20191.5.0.0noneOpenLDAP access log synchronization (contributed by Jonathan Gietz)
Object class handling improvements (contributed by Matthias Wolf)
Experimental support for "language-tagged" attributes.
Fix of security vulnerability: missing check of certificate validity.
2.2Polygondownload jarGitHub31st May 20191.5.0.0TBD

Upgrade of Apache Directory API (may fix some connection issues)
Support for substring filter anchors (MID-5383)
Fixing localization of configuration properties

Interoperability

In theory the connector should work with any LDAPv3 compliant LDAP server. However, many servers claim LDAPv3 compliance while the reality is far from ideal. The connector supports "quirks" of several popular LDAP servers and it tolerates some violations of LDAPv3 standards.

The connector was successfully tested with the following LDAP servers (assuming reasonably recent versions of the servers):

We know that at least some operations of the connector works with these servers and they are supported in some midPoint deployments. However, support for any specific server is not part of standard midPoint subscription and it has to be negotiated separately (see below).

If you are using this connector with a different directory server please let us know. We would like to know both about the positive and negative experiences.

Support

LDAP connector is bundled with midPoint distribution. Support for LDAP connector is included in standard midPoint support service (a.k.a. bundled support) - however, there are limitations. This "bundled" support only includes operations of LDAP connector that 100% compliant with LDAP standards. Any non-standard functionality is explicitly excluded from the bundled support.

It is a sad fact that so far we haven't seen any LDAP server that would be 100% standard-compliant or that would not require any non-standard extensions to work. Therefore if you want to be sure that this LDAP connector will work with your LDAP server, we strongly recommend to negotiate support for that specific server in your midPoint support contract.

For the purposes of this definition "standard" means RFC specifications that reach at least a "proposed standard" status. Drafts, informational documents, vendor specifications or any other documents are not considered to be part of LDAP standards.

This means that the bundled support does not include support for any specific LDAP server. Support for specific servers needs to be explicitly negotiated in the support contract.

There may be exception to this rule for the customers that purchased support before the release of midPoint 4.0. In case of any doubts please contact Evolveum sales representatives.

Documentation

See LDAP Connector Documentation

Resource Examples

Notes

The LDAP connector bundle also contains connectors for Active Directory and eDirectory. These connectors are specializations of the LDAP connector and support the LDAP quirks needed to work with AD and eDirectory.

See Also