[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: set ACL specification/syntax

To: Quanah Gibson-Mount <quanah@zimbra.com>
Subject: Re: set ACL specification/syntax
From: Andrew Cobaugh <phalenor@gmail.com>
Date: Fri, 6 Mar 2009 16:56:15 -0500
Cc: openldap-software@openldap.org
In-reply-to: <3BF6E9A9D6601F112E497DE9@192.168.1.199>
References: <1b8d56200903061246m421168b7ldd43daeee68538e8@mail.gmail.com> <468FA7BC840673FD209B06CC@192.168.1.199> <1b8d56200903061304q6675db68p25a977331fe5ef29@mail.gmail.com> <1b8d56200903061310xb47ac1cl6ebce3d13f4e9d5f@mail.gmail.com> <E84DB0EE804AA02B28E32E84@192.168.1.199> <1b8d56200903061338y47f350e2wdd9c1ec8616d6c4a@mail.gmail.com> <3BF6E9A9D6601F112E497DE9@192.168.1.199>

On Fri, Mar 6, 2009 at 4:45 PM, Quanah Gibson-Mount <quanah@zimbra.com> wrote:
> Which ACL is "This ACL"?

access to dn.subtree="ou=group,dc=mydomain"
    by set="this/cn & user/uid" write

> Have you turned on acl level debugging to see what exactly is occurring when
> you go to do operations?

Yes, and it is falling right past the above acl and hitting the
catchall for the top of the directory for * read.

> Also, what OpenLDAP release are you using?

Heh, OpenLDAP 2.4.11. Old I know, I've been meaning to go back to a
stable 2.3 for some time, but 2.4.x had certain fixes for the
translucent overlay that I needed, which I don't need anymore.

--andy

References:
- set ACL specification/syntax
  - From: Andrew Cobaugh <phalenor@gmail.com>
- Re: set ACL specification/syntax
  - From: Andrew Cobaugh <phalenor@gmail.com>

Prev by Date: "slapadd could not parse entry" & "ldap_add: Invalid syntax (21)" errors
Next by Date: Re: "slapadd could not parse entry" & "ldap_add: Invalid syntax (21)" errors
Index(es):
- Chronological
- Thread