[Tickets #14513] Changes LDAP Addressbook sync to ActiveSync

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/14513
------------------------------------------------------------------------------
  Ticket             | 14513
  Created By         | oliverafg at gmx.de
  Summary            | Changes LDAP Addressbook sync to ActiveSync
  Queue              | Turba
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


oliverafg at gmx.de (2016-11-12 00:44) wrote:

Hi,

I am not sure if I am doing something wrong. but I think it is a bug.

I use some LDAP backends as personal addressbook, group addressbooks  
(synced) and GAL.

The problem is per definition only for addressbooks synced on the  
mobile devices.

If I change something on the ActiveSync device or the Horde (turba)  
webfrontend, everything is synced fine and almost instant.

If I change it with an LDAP browser or e.g. Evolution, the changed or  
new entries do not show up on the Active Sync devices. Probably horde  
doesn't "want" to ask the LDAP for changes on every heartbeat. the  
only workaround so far, seems to be a complete re-sync triggered by  
horde or the mobile device.

In my opinion two options:
1) Maybe a counter the check for each device after every e.g. 4 hours  
for LDAP changes. This requires synced clocks on horde and the LDAP  
backend or some minutes security.
2) Maybe use a hash table and hash all LDAP entries every 4(?) hours.  
Needs also a counter for each device/user pair.

The counter stuff is bundled to an active devices, because the  
credentials are needed...

Thanks and regards