[turba] Unable to get Address Book in Compose.

[Jan Schneider]

Zitat von ANANT S ATHAVALE <asa at isac.gov.in>:

> ----- Message from Oscar del Rio <delrio at mie.utoronto.ca> ---------
>    Date: Sat, 31 Aug 2013 11:50:55 -0400
>    From: Oscar del Rio <delrio at mie.utoronto.ca>
> Subject: Re: [turba] Unable to get Address Book in Compose.
>      To: turba at lists.horde.org
>
>> On 30/08/2013 12:24 AM, ANANT S ATHAVALE wrote:
>>> Read failed: (32) No such object
>>
>> Googling that error, it seems to come from LDAP.  Check your LDAP
>> configuration.
>>
>> --
>> turba mailing list
>> Frequently Asked Questions: http://wiki.horde.org/FAQTo unsubscribe,
>> mail: turba-unsubscribe at lists.horde.org
>
> ----- End message from Oscar del Rio <delrio at mie.utoronto.ca> -----
>
> Dear Oscar,
>
> I could debug the problem.  It is not the problem with LDAP
> configuration.  I don't know, whether to say it is a bug of turba.  I
> think, developers will be able to understand.  The problem is as below.
>
> I have some contact lists in my address book.  Say, contact list 'one'. 
> I search for somebody in LDAP Address Book and using the search result
> output, I add one of the searched output to contact list 'one' and like
> this, I keep adding the entries in contact list.  This process was done in
> old version of HGWE.  Problem with these kind of additions is, the turba
> in localsql stores the entry with full 'dn'.  ie. it stores it like
> "anant,ou=a, ou=b, ou=c,dc=in". 
>
> Now, in earlier versions of turba, if there is no entry in ldap with the
> above dn, it used to ignore.  Now, in this version, if there no such 'dn',
> it is coming out with error.

Please create a ticket.

> I have told in my earlier postings also that, why to store the complete
> 'dn' in localsql for contact lists?  When a search is done on LDAP and use
> the result entries  in contact list, instead of storing dn, just store the
> minimal required fields like 'NAME' and 'EMail id', so that, even if the
> LDAP dn changes for a person, the contact list will not get affected.

This doesn't make any sense. DNs are supposed to be immutable. Most  
other attributes can change. That's why DNs are used as IDs.
-- 
Jan Schneider
The Horde Project
http://www.horde.org/