Add subentry OIDs to schema (OidRegistry)

• Key: DIRSERVER-404
• Type: Sub-task
• Status: Closed
• Resolution: Won't Fix
• Priority: Major
• Assignee: Alex Karasulu
• Reporter: Alex Karasulu

Description

On startup the following OIDs from RFC 3672 must be present within the OID registry:

        OID NAME
        -------- -------------------------------
       2.5.23.1 autonomousArea
       2.5.23.2 accessControlSpecificArea
       2.5.23.3 accessControlInnerArea
       2.5.23.4 subschemaAdminSpecificArea
       2.5.23.5 collectiveAttributeSpecificArea
       2.5.23.6 collectiveAttributeInnerArea

These are possible values for the administrativeRole attribute within the administrative point underwhich subentries reside. The values for this multivalued attribute will determine which subentries are valid under an administrative point.

Comments

[Alex Karasulu]

We don't really need to do this. It is hardcoded into the subnetry implementation instead. Which has the same effect.