[Date Prev][Date Next]
dn.dnstyle=dn acl works in backend specific but not in global configuration.
- To: openldap-software@OpenLDAP.org
- Subject: dn.dnstyle=dn acl works in backend specific but not in global configuration.
- From: jay alvarez <firstname.lastname@example.org>
- Date: Sun, 3 Jul 2005 22:14:42 -0700 (PDT)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=MkkNZJZmPQOpdUrswTs8pjfiIhjtcfMoQTyvZKrxPCufUkKGcegrd7Did8FJXbAuZxqKITMSzQH3mGXhDzY/Aqt+y59VtlvxxMRVXR6sJeMnbprXcVpv3LO60Rek4Sq/k0Gp3Plardub5uKZUCJZMrhPf1Gtu3IHVkCdcmnU148= ;
this is my access list:
access to dn.subtree="ou=staff,dc=preginet" by users
But my problem is that this only works when I place it
in database specific. slapd.conf(5) didn't mention
anything about this, it only says that configurations
placed in global or otherwise above any other
database/backend directive lines, can be overriden by
the configuration that are found below any
database/backend definition. I'm using version 2.2.26.
Apparently this was the answer I was looking for from
my previous posts regarding the error of always having
a bad DN.
Any input will be appreciated.
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.