Configuration of users, creation of user.xml

Learn how to create users in connector SE.

During synchronization, connector and CRM.interface impersonate the user which is assigned to the particular mailbox. connector authenticates itself both against Exchange Server and CRM.interface using these two technical accounts (see also topic General features).

The credentials (username and password) of these technical users are stored in an encrypted XML file - users.xml.

Use update.Users.exe – which is installed in the installation directory of connector SE- to create or modify the users.xml file.

For On-premise access, you just need to enter the User and Password for authentication.

For On-line exchange access, enter the details in the User Azure Details window as below:

Field	Description
User	Enter your Office365 email address.
Client Id	Enter Client Id from Azure active directory. See Configuring OAuth in Azure active directory admin center.
Client Secret	Enter Client Secret from Azure active directory. See Configuring OAuth in Azure active directory admin center.
Tenant	Enter Tenant from Azure active directory. See Configuring OAuth in Azure active directory admin center.
Scopes	Enter `https://outlook.office.com/.default`.

Default User Configuration

Note: "EWS Impersonation User" are the credentials of the user configured and created in Step Creating a technical user and configuring the impersonation for connector SE on Exchange Server 2010 above.

You can not only specify this user in the format: domain\username but also via SMTP address.

"EWS Connector Master" are the credentials of the Aurea CRM user.

In case of accessing Aurea CRM this security token is a base-64 encoded and RC2-128 encrypted string containing, among others, timestamps and the user name and password of the Administrator (OCSU) in the Aurea CRM database. The token is created based on information stored in the users.xml. The file contains machine-dependent keys and therefore needs to be created on the machine where the connector is installed. If such a token is authenticated successfully and the user name matches the configured master user, the system is able to log on to another user's account on the server without requiring password verification.

Note: The specified master user has to exist in Aurea CRM (for further details see Creating a Master User in Aurea CRM), the impersonation user has to exist in the Exchange organization.