Schema gurus...

According to documentation the groupOfURLs object is "an auxiliary object class of groupOfUniqueNames or groupOfNames" -
http://docs.sun.com/source/816-6682-10/oc_dir25.htm#1303745

This is also evident by being able to create both static and dynamic group members in a single group entry using iPlanet Console 5.0. Subsequent searches on the object reveal its objectclass is top-groupofuniquenames-groupofurls with both uniqueMember and memberURL attributes.

Both the 5.0 00core.ldif file and an ldapsearch on "cn=schema" however reveal groupOfURLs is STRUCTURAL which I think means it cannot also be a (structural) groupOfUniqueName object.

objectclasses=( 2.16.840.1.113730.3.2.33 NAME 'groupOfURLs' DESC 'iPlanet defined objectclass' SUP top STRUCTURAL MUST cn MAY ( memberURL $ businessCategory $ description $ o $ ou $ owner $ seeAlso ) X-ORIGIN 'iPlanet Directory Server' )

Is the schema wrong (should be AUXILIARY instead of STRUCTURAL) or is the implementation wrong (members can be static XOR dynamic), or have I missed something?

 

 

The DS makes no distinction between STRUCTURAL and AUXILIARY.

 

 

Thanks for the quick reply.

So it sounds to me like the 00core.ldif file (where some objectClasses are marked auxiliary) should reflect both the documentation (which explicitly says auxiliary) and actual behavior. This winds up being important if one is trying to implement an LDAP server supporting groupOfURLs.

Any idea where I can ask for an authoritative reply and possible correction to 00core.ldif (if in fact it is erroneous)?

 

 

Just follow up with your support channel.