Connector SE vs Connector for Domino

This topic explains how universal connector designed to support multiple messaging platform as compared to other connector.

CRM.connector universal is based on standard protocols and intended to support as many messaging systems as possible. Therefore connector is built on a subset of the functionality of connector SE and connector for Domino, which is implemented by all the systems. This consideration is the major reason for technical and functional differences.

Synchronization database

One of the main differences between connector universal and the other connectors is that connector universal requires a (local) SQL server database.

Note: Basically you can use any edition (e.g. Express Edition, Standard Edition etc.) of the SQL Server generations 2008 R2, 2012 and 2014. Explicit tests are performed with MS SQL Server 2012 Express Edition and SQL Server Native Client 11.0.

During the installation you have the option to install a local MS SQL Server 2012 Express Edition or to connect to an existing SQL Server instance.

Connector uses a SQL Server database to store:

Information about which e-mails already have been synchronized. See section below, Storage of synchronization information.
Information about the users whose mailboxes are synchronized. See section below, Authentication - Access of mailboxes, User management.

Storage of synchronization information

Connector does not store the synchronization information (e.g. the key of corresponding data records in Aurea.CRM and the status of the last synchronization) on the message level but in a separate (synchronization) database, except in case of Microsoft Exchange Server and Domino Server.

Authentication - Access of mailboxes, User management

Connector SE and connector for Domino both use a privileged account to impersonate the user's mailbox.

In case a messaging system does not support 2-legged authentication, connector requires the credentials of every user whose mailbox should be synchronized in order to access their mailboxes.

The credentials (SMTP address and password) are stored in the connector database (see Connection Settings). The user's passwords are encrypted with the key specified in the users.xml.

Most of the messaging systems do not support impersonation or other ways of 2-legged authentication.

Support for 2-legged authentication

Messaging Systems	2-legged authentication supported
Gmail	Yes
Open-Xchange	No
Zarafa	No
Zimbra	No

Note: Impersonation is only available to Google Apps for Business and Education accounts.

When Impersonation is used, ensure that the user account has a mailbox assigned to it on the correspondent platform.