eDirectory Connector

Last modified 22 Apr 2021 17:31 +02:00

Legacy LDAP-based connector for eDirectory servers.

Functionalitystable
Development statusabandoned (no longer developed or maintained, legacy code)
Support statusunsupported
OriginEvolveum
Support provided by
Target systemsNovell/NetIQ eDirectory
ProtocolLDAP/LDAPS
Source code
Legacy, unsupported

This connector was part of LDAP bundle for many years. However, there is no demand for this connector among midPoint subscribers. Therefore this connector is considered to be a legacy and was removed from LDAP bundle.

This connector is an eDirectory-specific extension of our LDAP connector. It contains, among others, support for the following attributes:

  • user (inetOrgPerson) attributes: groupMembership and securityEquals for maintaining referential integrity

  • group (nestedGroupAux) attributes: equivalentToMe and member

See this link for reciprocal attributes overview.

Based on Apache Directory API. Apache-licensed.

Capabilities and Features

Schema YES

Provisioning

YES

Live Synchronization

YES

Only using modifyTimestamp, but untested.

Password

YES

Activation

YES

loginDisabled attribute is used

Filtering changes

currently limited

Paging support

YES

Simple Paged Results and VLV

Native attribute names

YES

Use ri:dn instead of icfs:nameUse ri:entryUUID instead of icfs:uid

History

This is an extension of the LDAP connector completely rewritten from scratch.

Versions

Version Origin Binary Sources Build Date Description

1.4.2.0

Polygon

download jar

GitHub

August 2015

Official release

1.4.2.18

Polygon

download jar

GitHub

August 2015

Official release. Minor changes.

Documentation

Be advised there are multiple interesting limitations within the eDirectory (not midPoint):

  • CN attribute has a maximum size of 64 characters

  • subsequent white spaces (e.g. spaces) and underscores in the attribute values are considered to be the same as single space, so the following objects are considered to be the same and cannot be created simultaneously:

    • "cn=this is a space,ou=people,o=example"

    • "cn=this is a space,ou=people,o=example"

    • "cn=this is a space ,ou=people,o=example"

    • "cn=this\_is\_a\_space,ou=people,o=example"

    • "cn=___this\___is___a\___space,ou=people,o=example"

  • searching for values with whitespace e.g. "cn=a__b____c" may actually return object "cn=a b c,ou=people,o=example".