[Tickets #13197] (32) No such object

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13197
------------------------------------------------------------------------------
  Ticket             | 13197
  Created By         | asa at isac.gov.in
  Summary            | (32) No such object
  Queue              | Turba
  Version            | 4.1.4
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


asa at isac.gov.in (2014-05-21 10:47) wrote:

As per my knowledge, the problem is due to contact lists stored in
local address book created using LDAP objects.  The way the object of
LDAP is stored in localsql is w.r.t the full hierarchy. For example,
userA is stored as 'cn=userA,ou=A, ou=B, ou=C,dc=xx' in localsql/local
address book for a contact list entry.  If there is any change in
hierarchy of UserA in LDAP, we get this error.  In Horde 3, the
specific object like 'UserA' was not getting listed in contact list
contents, if there is a change in Hierarchy in LDAP for that specific user.

The requirement is, in case, if it is not able to fetch specific entry  
at the hierarchy stored, it should just skip that entry instead of  
giving error.