ABSTRACT:
ADSI and LDAP issues
DETAILED DESCRIPTION
There have been some issues reported about problems with ADSI and Novell LDAP Servers NDS eDirectory version 8: The main problem has been the inability to get all of the schema attributetypes (properties).
In investigating this there were five schema output differences that ADSI does not accept and therefore does not cache the information. The only information that the client displays is what has been cached.
These differences are:
ADSI requires the SYNTAX OIDs to be single quoted. This is not the standard spelled out in RFC2252. However Netscape does it this way and NetWare 5 did it this way, in NDS eDirectory version 8 we changed the output to match the standard in RFC2252.
The RFC2252 also talks about an upper bound that follows the SYNTAX OID, so in NDS eDirectory version 8 the upper bound was added where there was one. ADSI does not handle the upper bound being present.
RFC2252 specifies X- options in the definitions, these are for NDS specific data and ADSI does not ignore these like the RFC states should be done.
RFC2252 states there can be muliple names like ( ?cn? ?commonName? ). ADSI does not support multiple names.
For attributes or classes that do not have an OID defined the netscape default is to use "attributename-oid" all lower case. In NDS eDirectory version 8 Novell used the attribute name and appends a -OID for the OID, ADSI does not accept any upper case characters and only one dash. So if the name had an uppercase letter like commonName it would come out "commonName-OID" and not be valid. In the next release of eDirectory these will be converted to all lower case "commonname-oid"..
In talking with Microsoft they are now aware of the issues and hopefully will have ADSI accept a wider range of data.
--devsup
© 2008 Novell, Inc. All Rights Reserved.
