My very first guess is that openLDAP does access checking for every entry and
attribute that matches your filter criteria. rootDN is probably checked first
and fastest...
>>> "Jancewicz, Russell" schrieb am 06.11.2013 um
19:48 in Nachricht <50804e7d-6aeb-4480-8b45-fb24e3501...@ad.uconn.edu>:
>
Respectfully Submitted,
R. Toby Richards
Network Administrator
Superior Court of California
In and for the County of San Luis Obispo
(805) 781-4150
--On Wednesday, November 06, 2013 7:58 PM + "Jancewicz, Russell"
wrote:
The system currently has around 30 olcAccess stanzas, the majority of
which utilize the set notation to grant access based on groups. I
decided it might be wise to test the speed of the search using ldapi:///
and the
On Nov 6, 2013, at 14:26, Quanah Gibson-Mount wrote:
> --On Wednesday, November 06, 2013 6:48 PM + "Jancewicz, Russell"
> wrote:
>
>> Just before turning to this list i gave one last shot in the dark attempt
>> running my query using the rootDN. This produced the expected results.
>>
>>
--On Wednesday, November 06, 2013 6:48 PM + "Jancewicz, Russell"
wrote:
Just before turning to this list i gave one last shot in the dark attempt
running my query using the rootDN. This produced the expected results.
When queried with a typical account DN my system was transmitting around
On Wed, 6 Nov 2013, Jon C Kidder wrote:
> I am running 2.4.36 in my sandbox environment and have recently found
> myself needing to rename some entries in my directory. Slapd is
> reporting an object class violation when attempting to rename the
> entries even though all required attributes are
--On Wednesday, November 06, 2013 6:46 PM + Jon C Kidder
wrote:
As you can see from the ldif the cn attribute is clearly present. I am
assuming this is a bug and needs reported but wanted to review it with
the list members before I submitted the ITS entry.
slapd is doing exactly what yo
Jon C Kidder wrote:
> I am running 2.4.36 in my sandbox environment and have recently found myself
> needing to rename some entries in my directory. Slapd is reporting an object
> class violation when attempting to rename the entries even though all
> required attributes are present on the entr
Hello,
I am experiencing a bit of an issue with mdb network traffic.
When I request large queries (entire subtrees) from remote hosts my searches
take hundreds of times longer to complete than they do if I search on the local
machine (in all expect for one case).
I have attempted to tune the k
I am running 2.4.36 in my sandbox environment and have recently found myself
needing to rename some entries in my directory. Slapd is reporting an object
class violation when attempting to rename the entries even though all required
attributes are present on the entry. I have a sample ldif tha
Hi,
I have 2 Openldaps that are configured for replication one is on site, the
other is a remote. They are connected via a VPN tunnel and every time there is
a connection problem between the two the replication fails, but I have to
stop the services on the remote, delete the database and
On Wed, 06 Nov 2013 11:10:09 +0100 "Ulrich Windl"
wrote
> This is probably a stupid question, but I wonder:
> In the schema definitions, neither "gn" nor "sn" have a "syntax" attribute.
> So I wonder: If an attribute has a "sup", is the syntax inherited from the
> "sup" ("name" in this special cas
Hi!
This is probably a stupid question, but I wonder:
In the schema definitions, neither "gn" nor "sn" have a "syntax" attribute. So
I wonder: If an attribute has a "sup", is the syntax inherited from the "sup"
("name" in this special case)?
In Perilish:
DB<27> x $s->attribute('sn')
0 HASH(0
13 matches
Mail list logo
