Schema extension [extend] and ldap v3 conformance [proprietary]

Question

Hi,
am I still conform to ldap v3 spec when I extend the schema with my own attributes and object classes (with the iplanet console 5.1)?
So, does ldap v3 only define the object classes and attributes or an extension mechanism too?
Regards
Kristian

Answer 1

The first example was almost correct !
The error message: "javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001C6, problem 2001 (NO_OBJECT), data 0, best match of: 'CN=Schema,CN=Configuration,DC=ric,DC=com'; " simply indicates a naming error.
If you follow the logic of your code, you are trying to create an attribute with the distinguished name:[code]CN=fooattr,CN=Schema,CN=Configuration,DC=ric,DC=com,CN=Schema,CN=Configuration,DC=ric,DC=comIf you are wondering why, it is because you are attempting to create the subcontext from the schema naming context.schema.createSubcontext("CN=fooattr," + dn,attr);You can correct this by changing your code toschema.createSubcontext("CN=fooattr",attr); or toctx.createSubcontext("CN=fooattr," + dn,attr);One other error, you are missing one of the mandatory attributes; namely oMSyntax.attrs.put("oMSyntax","2");You can find details on the Active Directory Schema at http://technet2.microsoft.com/WindowsServer/en/library/97cae647-d996-48ff-b478-c96193abeadb1033.mspx
A simple way of checking the mandatory attributes for any object class is to look at the values of the systemMustContain attribute of the objectClass definition. In the case of attributeSchema, the systemMustContain attribute includes: schemaIDGUID (automagically generated), oMSyntax, ldapDisplayName, isSingleValued, cn, attributeSyntax and attributeID
Another reference that is helpful is a table of Attribute Syntax definitions at http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/distrib/dsbe_ext_dghb.mspx
The only words of advice for extending the schema are:
1. Test, Test, Test, before deploying in production
2. Do not ever reuse attributeID's or make up your own! If you are extending the schema get your own OID from an appropriate standards authority, or they may be obtained from Microsoft. Refer to http://msdn2.microsoft.com/en-us/library/ms677621.aspx or http://msdn2.microsoft.com/en-us/library/ms677620.aspx