Please add NetIQ eDirectory to that list (it's quite common in corporate environments both as authentication directory and basis for NetIQ Identity Manager), though it's LDAP v3 compliant and I've not seen any issues with Dirstudio that would require eDirectory-specific workarounds.
> Am 14.07.2015 um 14:26 schrieb Emmanuel Lécharny <[email protected]>: > > Le 14/07/15 12:12, Pierre Smits a écrit : >> Hi all, >> >> <quote>And a good LDAP API should support even bad servers</quote> >> >> Is that an achievable goal? Crappy servers pose so many exceptions to the >> rule, that any project, trying to realise a client solution, will >> eventually find that has shot itself in the foot. Of course, no one can >> argue with a contributor scratching his own itch. But shouldn't this be >> done in a separate dev branch, so that trunk isn't affected until such an >> integration is tried, tested and accepted? > There are not that many LDAP servers out there we need to support : > - ApacheDS > - OpenLDAP > - i389 > - AD > - IDS > - OID > - OpenDS > > My take is that most of them are pretty complients, except afor a few > things that are not correctly implemented. >
