Catalog authentication
The following table contains information about the requirements of the respective catalogs for authentication.
| Catalog | Authentication |
| ldap | Authentication requires a logon, password, and a domain for establishing the connection. The connection is created using ldap://domain. |
| ps | In addition to a logon and password, you also need to specify a PowerShell URL (default value for Microsoft Office 365) and an authentication mode (default value is basic). |
| azure | With Azure AD, logon and password are not configured in the conventional sense. ELOxc is registered as an app In Azure for the catalog query, which generates an app ID that is used as the logon. The password is either a secret key generated during app registration or the name of a certificate assigned to the app registration. You need to make this selection in the field "Azure authentication mode". Finally, you need to enter the client ID for Microsoft Office 365. |
| ews | EWS requires a logon, password, and SMTP address. You may also need to specify a URL for validating Autodiscover redirects if the Autodiscover service is outside the local domain. |
Impersonation
The difference between catalog authentication and authentication for mailbox processing via EWS is that impersonation is required to allow the ELOxc service account to access other mailboxes.
Mailbox catalogs, impersonationThe service connection does not even require impersonation rights to create a catalog. In addition, the EWS catalog is only one possible interface and only recommended in practice if no other catalog interface is available and you do not want to manually maintain a mailbox catalog.