Integration › Clients

Microsoft Teams

Add a Microsoft Teams Client interface and access your contact data in Microsoft Teams.

Hint

This Client interface is used by Contacts by XPhone. The description of the configuration in this chapter is limited to the Client Interface. The complete instructions for Contacts by XPhone can be found at:

https://help.c4b.com/cbyx/de/admin/index.html

Configuration

1. Open the directory administration interface and add the Client interface of the type Microsoft Teams (via Contacts by XPhone).

   • You can find out exactly how this works in these chapters:

     • Open the administration interface.

     • Adding client interfaces.

2. Configure the Basic settings

3. Configure IP & Port

4. Configure the Alternative identity

   Alternative identity

   XPhone Connect Directory can dynamically change the user context within an LDAP query. This allows specially customized applications to access personal contact data via LDAP. The LDAP client, together with suitable security settings, must ensure that no misuse is possible.

   • Identification features

     If you want to use the alternative identity, activate the option Activate alternative identity via filter condition in the LDAP query and then select how the users are to be authenticated via Identification feature. The authentication of the user takes place via the LDAP filter element :authentication:=<value>. For each search query, an attempt is made to find the value <value> in the user data of the Active Directory or in the XPhone Connect Server user administration.

   • Safety instructions

   Be sure to read and confirm the safety instructions.

   The alternative identity is only required if…

   • …data sources are set up for personal contact data…

   • …and the LDAP clients are not able to authenticate the owner of the personal contact data via the LDAP login. This is usually the case with server applications or telephone systems.

   The XPhone Connect Directory therefore offers the option for these applications to include the identity of the user for whom the query is being executed in the LDAP request. The identity is determined by any user-specific characteristic that is known to the LDAP client and that is checked against an attribute in the Active Directory or in the XPhone Connect Server user administration (e.g. phone number, MAC address, user name).

   With the Alternative identity option, the authentication security of the XPhone Connect Directory is disabled for this client interface. Please note the following:

   • The LDAP client must perform the authentication.

     The LDAP client (e.g. a telephone system, a terminal device or another server application) that accesses this client interface must ensure that this identification feature is only used correctly for authenticated users. This means that the LDAP client is responsible for authentication.

   • Protection of the LDAP client against unauthorized access.

     If an LDAP client is not able to perform authentication, it must be ensured that no unauthorized intervention can take place in its functionality (in particular the configuration). If it is possible to configure the client without authorization in such a way that a false identification feature can be incorporated into the query, the confidentiality of the contact data in personal contact data directories is no longer guaranteed.

   • Protection of the connection between LDAP client and XPhone Connect Directory.

     The connection between the LDAP client and the XPhone Connect Directory must be secured in the following way:

     • Set up TCIP/IP connection only via SSL (LDAPS) (see client interface configuration IP & Port).

     • Activate the login via name/password in the configuration of the client interface under authentication. Always choose a sufficiently long password. We recommend at least 30 characters in random order with the additional use of special characters and numbers. Switch off Anonymous login.

     • You can also restrict the range of permitted IP addresses by making the appropriate settings in the configuration of the client interface under Security.

     • If possible, restrict the accessibility of the network connection by using VLANs or by configuring switches, gateways and firewalls accordingly. Under no circumstances should you operate secure and unsecure clients on the same client interface.

   If in doubt, do not use the Alternative identity function.

5. Configure Security

6. Configure the Phone number conversion

7. Configure the Restricting the number of hits

8. Configure the Overview