| Summary | (32) No such object |
| Queue | Turba |
| Queue Version | 4.1.4 |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | |
| Requester | asa (at) isac (dot) gov (dot) in |
| Created | 05/21/2014 (4040 days ago) |
| Due | |
| Updated | 04/15/2015 (3711 days ago) |
| Assigned | |
| Resolved | 04/15/2015 (3711 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
Ticket: 13941State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ (32) No such object
Queue ⇒ Turba
Milestone ⇒
Patch ⇒ No
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.