6.0.0-alpha12
6/12/25

[#9871] A Personal Ldap address book cannot be synced with ActiveSync
Summary A Personal Ldap address book cannot be synced with ActiveSync
Queue Synchronization
Queue Version Git master
Type Bug
State Duplicate
Priority 2. Medium
Owners
Requester ryu (at) ryux (dot) org
Created 04/11/2011 (5176 days ago)
Due
Updated 05/19/2011 (5138 days ago)
Assigned
Resolved 04/19/2011 (5168 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
05/19/2011 07:58:34 AM ryu (at) ryux (dot) org Comment #5 Reply to this comment
The resolution of bug #9733  in Horde H4 4.0.3 solves this bug. Thanks
04/19/2011 05:01:49 PM ryu (at) ryux (dot) org Comment #4 Reply to this comment
What authentication backend is being used?
It is IMP which provides authentication with IMAP backend
04/19/2011 03:56:46 PM Michael Rubinsky Comment #3 Reply to this comment
What authentication backend is being used?
04/19/2011 03:45:23 PM Jan Schneider Comment #2
State ⇒ Duplicate
Reply to this comment
Duplicate of bug #9733.
04/11/2011 07:03:39 AM ryu (at) ryux (dot) org Comment #1
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Synchronization
Summary ⇒ A Personal Ldap address book cannot be synced with ActiveSync
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
I've a "Personal LDAP" address book and the synchronization with 
ActiveSync fails.
It is probably because the Registry is not correctly filled.

If I replace $GLOBALS['registry']->getAuth('bare') and 
$GLOBALS['registry']->getAuthCredential('password') in the turba 
backend configuration file by real value, it works.

The Shared LDAP address book works without problem.

Saved Queries