When returning contacts we have to supply also the domain field.
Because in a multidomain environment UIDField is unique only in
the domain so an user must be identified as uid@domain.
So when creating http requests from client side, we have to use
uid@domain instead of only uid so the SOGoUser created on server
side when parsing the requests is created properly.
When using dynamic domains with SQL sources (DomainFieldName),
let WebUI and dav lookups return entries from current domain
and other domains visible from the originating domain.
Fixes#2269
SQLSource.m: _visibleDomainsQualifierFromDomain:
returns a EOQualifier OR'ing all visible domains from specified domain
(including specified domain)
SQLSource.m: allEntryIDsVisibleFromDomain
Replacement for allEntryIDs.
Instead of returning all entries from the sql source,
only return the entries visible from the specified domain.
SoObjects/SOGo/SQLSource.m: allEntryIDs
Changed to call allEntryIDsVisibleFromDomain with an empty domain.
SQLSource.m fetchContactsMatching:inDomain:
Use _visibleDomainsQualifierFromDomain to filter entries
LDAPSource.m: allEntryIDsVisibleFromDomain
Simply call allEntryIDs, discarding the domain.
LDAP does need to do the extra domain filtering
SOGoContactSourceFolder.m: toOneRelationshipKeys
Call new method: allEntryIDsVisibleFromDomain
Restored the previous behavior: only the personal addressbook is
returned and only the first source directory is returned (now sorted by
id so you can control which of your addressbook sources you want to
return).
(-isAndroid): new method to detect whether the
request has been performed from an android client
* SoObjects/Contacts/SOGoContactFolders.m (appendSystemSources):
Let sogo append system sources if the request comes from an android
client even if its user agent matches the IPhoneAddressBook
Monotone-Parent: a4ef73c2ad79c8da8d8e0c93767ab06e14bc846b
Monotone-Revision: 228f7d730cde5a5046b0885c1ac02649ee2b7c05
Monotone-Author: jraby@inverse.ca
Monotone-Date: 2012-06-29T20:17:20
lost in last commit
Monotone-Parent: 06f33f8f7c4581f3ec39d5cce6e3b77a99d436b0
Monotone-Revision: 65528b04d38419185ed64db626bd6ae368bfcd00
Monotone-Author: jraby@inverse.ca
Monotone-Date: 2012-04-26T13:53:15
carry the c_info attribute in vcards through the x-sogo-contactinfo attribute.
This functionality was lost a while ago.
We used to use the NOTE attribute for this. From now on,
the sogo-connector.autoComplete.commentAttribute have to be set to
'unprocessed:x-sogo-contactinfo' instead of 'Notes'.
Monotone-Parent: d8a0de208631b406144e740ab09b4e5a92f0e66c
Monotone-Revision: 402b5b43e7c75b50806b41e7372eed0e61a4de9f
Monotone-Author: jraby@inverse.ca
Monotone-Date: 2012-04-25T21:35:29