[turba] No details for LDAP directory

[Jan Schneider]

Zitat von lst_hoe02 at kwsoft.de:

> Zitat von lst_hoe02 at kwsoft.de:
>
>> Zitat von lst_hoe02 at kwsoft.de:
>>
>>> Zitat von lst_hoe02 at kwsoft.de:
>>>
>>>> Zitat von Simon Wilson <simon at simonandkate.net>:
>>>>
>>>>>> Hello,
>>>>>>
>>>>>> we try to use a central LDAP directory as read only contact  
>>>>>> store with Turba latest. Searching works fine as of now but  
>>>>>> when clicking at the found entries to get the details for this  
>>>>>> entries Turba always show the error message "Not found" and  
>>>>>> jump back to the search screen. The LDAP source is listed  
>>>>>> below, the backend is "ESTOS MetaDirectory". We have tried  
>>>>>> different mappings for __key, but the result is always the same  
>>>>>> :-(
>>>>>>
>>>>>>
>>>>>
>>>>> ----- End message from lst_hoe02 at kwsoft.de -----
>>>>>
>>>>> This is what I have in ours, works fine as a GAL type read only  
>>>>> source. Is sync'ed through to ActiveSync devices as a global  
>>>>> address list too, which is handy.
>>>>>
>>>>
>>>> GAL works as expected also, but as said the details when klicking  
>>>> on the found entries in Turba does not work. We set browse and  
>>>> export to false because there are ~3000 entries available.
>>>>
>>>
>>> Any idea how to debug this??
>>>
>>
>> I have set the loglevel to "DEBUG" to see the LDAP request failing,  
>> but i only see one LDAP request which is the one from the search  
>> which is working. So clicking the name to get the contact details  
>> seem to do no further LDAP request but simply fail. Any idea what  
>> could cause the contact details to fail without a (LDAP) query??
>>
>
> The URL create is something like this  
> "https://webmail.kwsoft.de/turba/contact.php?source=localldap&key=589371882a9ebbe85234fe351de17561" which looks fine to me. The error message "Not found" is included in turba/edit.php and turba/deletefile.php but not in turba/contact.php. Can anyone comment on how to debug why no LDAP query is created for the URL  
> above??
>
> Thanks
>
> Andreas

This doesn't look fine at all. IIRC you mapped __key to dn, but this  
is definitely not a dn.
-- 
Jan Schneider
The Horde Project
http://www.horde.org/
https://www.facebook.com/hordeproject