Re: [ldapext] LDAP Groups topic split-out

Michael Ströder <michael@stroeder.com> Fri, 04 December 2015 15:36 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 295781A87B2 for <ldapext@ietfa.amsl.com>; Fri, 4 Dec 2015 07:36:31 -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 1-M-0Fr9v813 for <ldapext@ietfa.amsl.com>; Fri, 4 Dec 2015 07:36:29 -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 B43171A87AB for <ldapext@ietf.org>; Fri, 4 Dec 2015 07:36:28 -0800 (PST)
Received: from srv4.stroeder.local (unknown [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" (verified OK)) by srv1.stroeder.com (Postfix) with ESMTPS id 255F91CF66; Fri, 4 Dec 2015 15:36:26 +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 47F0B1D29F; Fri, 4 Dec 2015 15:36:26 +0000 (UTC)
To: Simo Sorce <simo@redhat.com>
References: <CAJb3uA57jHCfhN6tQB6Kc7uOGF3g4w6GVmr6+OnhD4=k5zqEzw@mail.gmail.com> <5660DF62.5000800@oracle.com> <1449242619.3445.50.camel@redhat.com>
From: Michael Ströder <michael@stroeder.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5661B2FA.2020204@stroeder.com>
Date: Fri, 04 Dec 2015 16:36:26 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 SeaMonkey/2.39
MIME-Version: 1.0
In-Reply-To: <1449242619.3445.50.camel@redhat.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms040606010505090102000501"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ldapext/g5QqbjVuDvK29UxKaNGJM-wL27o>
Cc: ldapext <ldapext@ietf.org>
Subject: Re: [ldapext] LDAP Groups topic split-out
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 04 Dec 2015 15:36:31 -0000

Simo Sorce wrote:
> in fact in our project we do populate memberof
> automatically based on the member attribute (including unrolling nested
> relationship for the pain of those that loves non-unrolled memebrofs in
> AD) but we also prevent access to the memberof attribute to some classes
> (like unauthenticated guest sessions, etc..).

But it was a fault to take the very same OID and NAME for that attribute like
'memberOf' in MS AD because the semantics are different there (no nested groups
referenced).

> The main issue with dealing with memberof is access control around the
> "add" operation.

Yupp. Needs value-based access control. Does 389-DS provide ACIs like this?

Ciao, Michael.