Tickets :: [#12917] Match the ActiveSync GAL search fields with Turba backend

6.0.0-beta1

8/18/25

Summary	Match the ActiveSync GAL search fields with Turba backend
Queue	Synchronization
Queue Version	Git master
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	lst_hoe02 (at) kwsoft (dot) de
Created	01/15/2014 (4233 days ago)
Due
Updated	10/07/2014 (3968 days ago)
Assigned	01/15/2014 (4233 days ago)
Resolved	01/18/2014 (4230 days ago)
Milestone
Patch	No

10/07/2014 05:39:46 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #9	Reply to this comment
The fix is actually in Turba. https://github.com/horde/horde/commit/e18ea0cfc2af154d59a6a262d9b0ddc037a3d3ad Thank you mike, this patch solved it!

10/07/2014 05:10:41 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #8 New Attachment: activesync_GAL_search.txt	Reply to this comment
The fix is actually in Turba. https://github.com/horde/horde/commit/e18ea0cfc2af154d59a6a262d9b0ddc037a3d3ad Look at the synclog and see what is actually being sent to the client.

10/07/2014 04:57:37 PM	Michael Rubinsky	Comment #7	Reply to this comment
There were too many results being found due to incorrectly specifying the fields to search. This results in too many contacts in the search result or not one? It depends. It could be so many that the maximum is reached, so the actual one you are looking for never makes it to the device. Still, the device can filter the results on it's own too so it's possible you would never see those that don't match the search string. Horde_Core 2.14.2 stable Horde_ActiveSync 2.19.3 stable The fix is actually in Turba. However, what is probably happening for you is that most clients will not display the result unless the name or email contains the searched text. I search for example the word "example", then I should find the contact with the mail address "name@example.com", true? At the moment I found it only if I search for the name. Look at the synclog and see what is actually being sent to the client.

10/07/2014 04:25:49 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #6	Reply to this comment
There were too many results being found due to incorrectly specifying the fields to search. This results in too many contacts in the search result or not one? Horde_Core 2.14.2 stable Horde_ActiveSync 2.19.3 stable However, what is probably happening for you is that most clients will not display the result unless the name or email contains the searched text. I search for example the word "example", then I should find the contact with the mail address "name@example.com", true? At the moment I found it only if I search for the name.

10/07/2014 04:09:56 PM	Michael Rubinsky	Comment #5	Reply to this comment
There was an issue, but it is the opposite of what you are seeing. There were too many results being found due to incorrectly specifying the fields to search. However, what is probably happening for you is that most clients will not display the result unless the name or email contains the searched text.

10/07/2014 03:02:58 PM	samuel (dot) wolf (at) wolf-maschinenbau (dot) de	Comment #4	Reply to this comment
Sorry for posting on this old enhancement. I set my LDAP address book for GAL, but search for a company doesn't show one result. Search for lastname or firstname work as expected. Is this a limitation of my smartphone (Motorola Razr i Android 4.1.2)? 'map' => array( '__key' => 'dn', 'name' => 'displayname', 'email' => 'mail', 'homePhone' => 'homephone', 'workPhone' => 'telephonenumber', 'cellPhone' => 'mobile', 'firstname' => 'givenname', 'lastname' => 'sn', 'company' => 'o', 'workStreet' => 'street', 'workPostalCode' => 'postalCode', 'workCity' => 'l', ), 'search' => array( 'name', 'email', 'workCity', 'company', 'firstname', 'lastname', ),

01/18/2014 10:59:31 PM	Michael Rubinsky	Comment #3 State ⇒ Resolved	Reply to this comment
Horde 5.2 / Horde_Core 2.12.0

01/18/2014 10:57:38 PM	Git Commit	Comment #2	Reply to this comment
Changes have been made in Git (master): commit ded00f09e430718a521f9da427e2651fd55b0142 Author: Michael J Rubinsky <mrubinsk@horde.org> Date: Sat Jan 18 17:56:35 2014 -0500 ~~Bug: 12917~~ Don't restrict fields for ActiveSync search requests. Always use the configured search fields according to the backend. .../Core/lib/Horde/Core/ActiveSync/Connector.php \| 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) http://git.horde.org/horde-git/-/commit/ded00f09e430718a521f9da427e2651fd55b0142

01/15/2014 04:23:15 PM	Michael Rubinsky	Assigned to Michael Rubinsky State ⇒ Assigned

01/15/2014 04:07:28 PM	lst_hoe02 (at) kwsoft (dot) de	Comment #1 Milestone ⇒ State ⇒ New Patch ⇒ No Queue ⇒ Synchronization Summary ⇒ Match the ActiveSync GAL search fields with Turba backend Type ⇒ Enhancement Priority ⇒ 1. Low	Reply to this comment
Extend the fields searched with ActiveSync GAL to match the fields configured for the Turba backend used. With this it is possible to search additional fields like "company" with GAL access.