Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 53890 invoked from network); 10 Sep 2005 04:08:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Sep 2005 04:08:33 -0000 Received: (qmail 14332 invoked by uid 500); 10 Sep 2005 04:08:32 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 14283 invoked by uid 500); 10 Sep 2005 04:08:32 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 14268 invoked by uid 99); 10 Sep 2005 04:08:32 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Sep 2005 21:08:31 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 5A5C3330 for ; Sat, 10 Sep 2005 06:08:30 +0200 (CEST) Message-ID: <111683264.1126325310338.JavaMail.jira@ajax.apache.org> Date: Sat, 10 Sep 2005 06:08:30 +0200 (CEST) From: "Alex Karasulu (JIRA)" To: dev@directory.apache.org Subject: [jira] Closed: (DIREVE-235) Add subentry OIDs to schema (OidRegistry) In-Reply-To: <909353231.1125398049254.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ 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