[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Using back-ldap as a client-side proxy/cache
>>
>> On 25 Mar 2010, at 01:15, Howard Chu wrote:
>>
>>> overlay pcache
>>> proxycache bdb 100 2 6 1m
>>> proxyattrset 0 uid userPassword uidNumber gidNumber gecos
>>> cn homeDirectory loginShell objectClass
>>> proxyattrset 1 cn userPassword gidNumber memberUid
>>> uniqueMember objectClass
>>> proxytemplate (&(objectclass=)(uid=)) 0 3600
>>> proxytemplate (&(objectclass=)(uidnumber=)) 0 3600
>>> proxytemplate (&(objectclass=)(gidnumber=)) 1 3600
>>> proxytemplate (&(objectclass=)(|(memberuid=)(uniquemember=))) 1 3600
>>> response-callback head
>>
>> Got it! My pcacheTemplates were written using original case
>> (objectClass,
>> memberUid, etc.), which gets normalized to lower case inside slapd (via
>> nssov). Hence external queries maintaining case would trigger pcache,
>> but
>> the internal ones didn't.
>>
>> D'oh!
>>
>> Changed the templates to lower case. All working now. Thanks, Howard.
>
> Your temporary fix is probably fine. Though, I'd consider this a bug: the
> case should not matter. I suggest you file an ITS.
Although I'm not quite seeing where in the code the case of that
configuration may matter.
p.