I am trying to get KAddressBook to use my LDAP server. No problem -- it does. However, any changes I make to LDAP entries via KAddressBook are not actually made back to the LDAP. Any changes made from other programs to the LDAP are not reflected in KAddressBook unless I restart Akonadi.

So, it appears that on first connection -- Akonadi / KAddressBook creates a local copy of the LDAP entries and any changes made to the LDAP locally are not copied back and any changes made remotely are not reflected locally.

I figure this is because Akonadi is caching the data and it just isn't synchronising. Is this a known bug, or at least known behaviour? Are there plans to fix this behaviour? Is there a way to turn caching off, or at least force it synchronise every so often. None of the options in KAddressBook or Akonadi seem to have any effect.

Thanks for any help / information.

Is the account you are using authorised to make changes to the LDAP directory? It could be a permissions issue. If you don't make any changes, does Akonadi keep itself up to date?

i have the same problem. with KDE 3.5 the LDAP-KAddressbooks works fine. Now with Akonadi i can't write back to our LDAP-Server - i think the Akonadi-Backend has a Problem but i don't know where.
FYI: Our LDAP Server needs a self-signed cert, but with the correct openLDAP.conf reading works.

edit: tested with KDE SC 4.6

There may indeed be bugs in KAddressBook's LDAP support. Please file a bug at bugs.kde.org.

I understand he can in fact write although he needs an akonadi restart.

The bug might not be about writing but refreshing cache, right?

Regards

Kaddressbook write the changed/new contact in the akonadi chache. After a restart of Akonadi, the contect is gone and not in out LDAP-Directory :cry: