[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Proxy cache not work with <attribute not in schema>
- To: openldap-technical <openldap-technical@openldap.org>
- Subject: Proxy cache not work with <attribute not in schema>
- From: JWD <j-wd@163.com>
- Date: Tue, 25 Oct 2016 11:04:19 +0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Subject:Mime-Version:Message-ID; bh=KN4H1 cHDK1wesiL2k74/ZMCobWMva75ar4v3JOxBRrY=; b=ER7yAfWVuesVTrXwqTGm0 IahOX9EV4WNT0dDpUAdUCSc9jR6JTrQbta2Q4ONyYuNi48LwtWfFHSf9SMQOlr1K 7BtazNe9dozuJ8Ppsto6L6hVuwHyFxGu+0uCf/cRocnReBcOK4ZmV92QauxCvThu czKOLohGlRodEnTQcDp5Sg=
slapd 2.4.40
Windows AD as proxy backend.
I found any query match <pcacheTemplate>+<pcacheAttrset>+<attribute not in schema> will answer <pcacheAttrset> value only, <attribute not in schema> will be ignored.
This is not what I expected, I need <attribute not in schema> too.
But query anything else that not in cache, <attribute not in schema> will be cached.
Log message like this:
580ec506 PROXIED attributeDescription "PRIMARYGROUPID" inserted.
And after that, query match <pcacheTemplate>+<pcacheAttrset>+<attribute not in schema> will answer <attribute not in schema> too.
This is what I expected.
Do I have to add schema for <attribute not in schema>?
Is there any other way to make <attribute not in schema> CACHEABLE?
--------------
JWD