Re: [ldapext] LDAP Groups topic split-out

Simo Sorce <simo@redhat.com> Fri, 04 December 2015 16:04 UTC

Return-Path: <simo@redhat.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 A65151A88A3 for <ldapext@ietfa.amsl.com>; Fri, 4 Dec 2015 08:04:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.611
X-Spam-Level:
X-Spam-Status: No, score=-6.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_HELO_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 Ml1tPmzN_oH2 for <ldapext@ietfa.amsl.com>; Fri, 4 Dec 2015 08:04:54 -0800 (PST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98ADD1A8824 for <ldapext@ietf.org>; Fri, 4 Dec 2015 08:04:54 -0800 (PST)
Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id 374E291346; Fri, 4 Dec 2015 16:04:54 +0000 (UTC)
Received: from willson.usersys.redhat.com ([10.3.113.3]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tB4G4qEC027171 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 4 Dec 2015 11:04:53 -0500
Message-ID: <1449245092.3445.71.camel@redhat.com>
From: Simo Sorce <simo@redhat.com>
To: Michael =?ISO-8859-1?Q?Str=F6der?= <michael@stroeder.com>
Date: Fri, 04 Dec 2015 11:04:52 -0500
In-Reply-To: <5661B2FA.2020204@stroeder.com>
References: <CAJb3uA57jHCfhN6tQB6Kc7uOGF3g4w6GVmr6+OnhD4=k5zqEzw@mail.gmail.com> <5660DF62.5000800@oracle.com> <1449242619.3445.50.camel@redhat.com> <5661B2FA.2020204@stroeder.com>
Organization: Red Hat, Inc.
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26
Archived-At: <http://mailarchive.ietf.org/arch/msg/ldapext/ZclxxY7V1i3lSTnIOd2ixtohznM>
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 16:04:55 -0000

On Fri, 2015-12-04 at 16:36 +0100, Michael Ströder wrote:
> 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).

I think fault or not is a matter of perspective, we do use this
attribute for members of a group, as the description says.
But yeah it behaves in a slightly different way than AD does and in
retrospect we may have used 2 separate attributes.

> > 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?

Yes, it actually does, but we do not allow to modify the memberof
attributes directly, we consider it an operational attribute (although
not marked as operational :-) which is always set through an operation
on the member attribute of the target group.

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York