Stable. Works well.
This is the recommended connector to connect midPoint with the LDAP servers.
Connector for LDAP-based directory servers. Complete rewrite based on Apache Directory API. Apache-licensed.
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.
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.
LDAP or LDAPS
For LDAP servers that support Sun-style changelog (Retro ChangeLog) or modifyTimestamp.
AD DirSync synchronization supported.
No activation for generic LDAP as there is not LDAP standard for that. This can be simulated in midPoint.
Simple Paged Results and VLV
|Native attribute names||YES|
Use ri:dn instead of icfs:name
Use ri:entryUUID instead of icfs:uid
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.
|Framework version||Bundled with midPoint|
LDAP stable, AD experimental
|184.108.40.206||Polygon||download jar||GitHub||June 2016||220.127.116.11||Fixes timeout errors and resource leaks during AD connector resets.|
|18.104.22.168||Polygon||download jar||GitHub||June 2016||22.214.171.124||3.4||Minor fixes.|
|126.96.36.199||Polygon||download jar||GitHub||September 2016||188.8.131.52||3.4.1||Minor improvements.|
|184.108.40.206||Polygon||download jar||GitHub||October 2016||220.127.116.11||Minor improvements.|
|1.4.3||Polygon||download jar||GitHub||December 2016||18.104.22.168||3.5||Minor improvements.|
|1.4.4||Polygon||download jar||GitHub||April 2017||22.214.171.124||3.5.1||CredSSP and Exchange powershell support, bugfixes, minor improvements.|
|1.4.5||Polygon||download jar||GitHub||3rd July 2017||126.96.36.199||3.6||Powershell bugfixes, minor improvements.|
|1.5||Polygon||download jar||GitHub||4th October 2017||188.8.131.52||3.6.1||More powershell execution alternatives and improvements, alternative auxiliary object class detection, explicit object class filter, configurable timestamp presentation, better error messages.|
|1.5.1||Polygon||download jar||GitHub||11th December 2017||184.108.40.206||3.7, 3.7.1||Release coupled with AD connector.|
|1.6||Polygon||download jar||GitHub||4th May 2018||220.127.116.11||3.7.2, 3.8||Release coupled with AD connector.|
|1.6.1||Polygon||download jar||GitHub||17th April 2019||18.104.22.168||TBD||Fix of security vulnerability: missing check of certificate validity.|
|2.0||Polygon||download jar||GitHub||7th November 2018||22.214.171.124||3.9||Native timestamp support. Support for delta-based updates. Additional search filter support.|
|2.1||Polygon||download jar||GitHub||17th April 2019||126.96.36.199||TBD||OpenLDAP 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.
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 supports following servers (assuming reasonably recent versions of the servers):
In addition to this the connector was successfully tested with the following LDAP servers:
We know that the connector works with these servers and they are supported in some midPoint deployments. However, support for these servers is not part of standard midPoint subscription and it has to be negotiated separately.
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.
See LDAP Connector Documentation