Re: [ldapext] Schema for posixGroup successor (RFC 2307 bis)

Michael Ströder <michael@stroeder.com> Thu, 12 February 2015 12:31 UTC

Return-Path: <michael@stroeder.com>
X-Original-To: ldapext@ietfa.amsl.com
Delivered-To: ldapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6AD31A1BFE for <ldapext@ietfa.amsl.com>; Thu, 12 Feb 2015 04:31:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level:
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s5t6Nd3aT-gO for <ldapext@ietfa.amsl.com>; Thu, 12 Feb 2015 04:31:06 -0800 (PST)
Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 074881A1AA3 for <ldapext@ietf.org>; Thu, 12 Feb 2015 04:31:05 -0800 (PST)
Received: from srv4.stroeder.local (srv4.stroeder.local [10.1.1.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.stroeder.local", Issuer "stroeder.com Server CA no. 2009-07" (not verified)) by srv1.stroeder.com (Postfix) with ESMTPS id EB8DA1CF7A; Thu, 12 Feb 2015 12:31:02 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by srv4.stroeder.local (Postfix) with ESMTP id B0C411D36D; Thu, 12 Feb 2015 12:31:01 +0000 (UTC)
X-Virus-Scanned: amavisd-new at stroeder.local
Received: from srv4.stroeder.local ([127.0.0.1]) by localhost (srv4.stroeder.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c3mTMDVeWs1A; Thu, 12 Feb 2015 12:30:55 +0000 (UTC)
Received: from nb2.stroeder.local (nb2.stroeder.local [10.1.1.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by srv4.stroeder.local (Postfix) with ESMTPS id 6DBF91CE20; Thu, 12 Feb 2015 12:30:53 +0000 (UTC)
Message-ID: <54DC9CFD.3010309@stroeder.com>
Date: Thu, 12 Feb 2015 13:30:53 +0100
From: =?UTF-8?Q?Michael_Str=c3=b6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 SeaMonkey/2.32.1
MIME-Version: 1.0
To: Ludovic Poitou <ludovic.poitou@gmail.com>
References: <54DB27C7.3060409@stroeder.com> <20150212102738.GC3229@slab.skills-1st.co.uk> <54DC8BD7.3040009@stroeder.com> <20150212114807.GG3229@slab.skills-1st.co.uk> <54DC941C.3070504@stroeder.com> <etPan.54dc9bdd.43f18422.15e@lpm.local>
In-Reply-To: <etPan.54dc9bdd.43f18422.15e@lpm.local>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030103070708030205080906"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ldapext/9t5Q2wwXtYTpAoET3JhMVvozOKU>
Cc: ldapext <ldapext@ietf.org>
Subject: Re: [ldapext] Schema for posixGroup successor (RFC 2307 bis)
X-BeenThere: ldapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LDAP Extension Working Group <ldapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ldapext>, <mailto:ldapext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ldapext/>
List-Post: <mailto:ldapext@ietf.org>
List-Help: <mailto:ldapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ldapext>, <mailto:ldapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2015 12:31:09 -0000

Ludovic Poitou wrote:
> I was trying to define the posixGroup2 object class in OpenDJ, and the
> server refuses it because we do not allow to define a structural
> objectClass that inherits from auxiliary objectClasses.

Then you have a schema installed which is not pure RFC 2307!

Probably you already have a RFC2307bis-like schema workaround added which
violates Kurt's IANA guidelines.

> And this is the proper behavior as RFC4512, section 2.4.2 specifically calls it:

Yes, mixed inheritance of STRUCTURAL and AUXILIARY object classes is not allowed!

Ciao, Michael.