You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2005/09/10 06:08:30 UTC
[jira] Closed: (DIREVE-235) Add subentry OIDs to schema (OidRegistry)
[ http://issues.apache.org/jira/browse/DIREVE-235?page=all ]
Alex Karasulu closed DIREVE-235:
--------------------------------
Resolution: Won't Fix
We don't really need to do this. It is hardcoded into the subnetry implementation instead. Which has the same effect.
> Add subentry OIDs to schema (OidRegistry)
> -----------------------------------------
>
> Key: DIREVE-235
> URL: http://issues.apache.org/jira/browse/DIREVE-235
> Project: Directory Server
> Type: Sub-task
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Fix For: 0.9.3
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira