Novell EDIRECTORY 8.8 - GUIDE, Manual

Page: 318 / 574

Understanding LDAP Services for Novell eDirectory 319
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
12.2.3 Enabling Nonstandard Schema Output
eDirectory contains a compatibility mode switch that allows nonstandard schema output so that
current ADSI and old Netscape clients can read the schema. This is implemented by setting an
attribute in the LDAP Server object. The attribute name is nonStdClientSchemaCompatMode. The
LDAP Server object is usually in the same container as the Server object.
The nonstandard output does not conform to the current IETF standards for LDAP, but it will work
with the current version of ADSI and old Netscape clients.
In nonstandard output format:
• SYNTAX OID is single quoted.
• No upper bounds are output.
• No X- options are output.
• If more than one name is present, only the first encountered is output.
• Any attributes or classes without an OID defined will be output “attributename-oid” or
“classname-oid” in lowercase.
• Attributes or classes with a hyphen in the name and no defined OID are not output.
OID or Object Identifier is a string of octet digits that is required to add an attribute or objectclass of
your own to an LDAP server.
To enable nonstandard schema output:
1
In Novell iManager, click the Roles and Tasks button .
2 Click LDAP > LDAP Overview .
3
Click View LDAP Servers , then click an LDAP Server object.
4 Click Searches , then click Enable old ADSI and Netscape Schema Output .
The nonstandard output does not conform to the current IETF defined standards for LDAP, but
it works with the current ADSI and old Netscape clients.
5 Click Apply , click Information , then click Refresh .
12.2.4 Syntax Differences
LDAP and eDirectory use different syntaxes. Some important differences include the following:
• “Commas” on page 319
• “Typeful Names” on page 320
• “Escape Character” on page 320
• “Multiple Naming Attributes” on page 320
Commas
LDAP uses commas as delimiters rather than periods. For example, a distinguished (or complete)
name in eDirectory looks like this:
CN=JANEB.OU=MKTG.O=EMA
Using LDAP syntax, the same distinguished name would be