---
title: Tenant Connector
slug: singleconnect-reference-guide-3-3-0/tenant-connector
description: Learn how to establish a highly secure remote data center connection using Single Connect's Tenant Connector feature. This comprehensive document provides step-by-step instructions for adding either an OpenVPN Connector or a Built-in VPN Connector. Additi
docTags: 
createdAt: 2022-12-05T09:02:30.000Z
---

The Tenant Connector provides secure remote data center connections to different tenants who want to use Single Connect’s features, such as preventing password theft and eliminating unsupervised access and need a secure connection between their remote data centers and the central Single Connect server. This section describes how the tenant connector is added and matched with devices.

To create an OpenVPN Connector:

### Adding an OpenVPN Connector

Tenants who already have an OpenVPN server in the remote data center or want to use OpenVPN in their remote data center connections can use this feature.

1. Navigate to **Tenant Connector**.
2. Open the **Connector Sites** tab.
3. Click the **Add** button, enter the remote site name and description, and click **Save**
4. Open the **Connector Nodes **tab.
5. Click the **Add** button and select the **OpenVPN** option.
6. Select the connector site, enter the OpenVPN credentials, copy the OpenVPN configuration, and click **Save**.

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/bXvVsrECEpHC43AK7z9___image.png "OpenVPN Connector Configuration Screen")

### Adding a Built-in VPN Connector

Tenants who do not have an OpenVPN license and want to use Single Connect’s secure connection can use its Built-in VPN option. Connectorinstallation packages are uploaded tofilerepo.krontech.com SFTP Server. The Kron support team provides credentials and the OVA installer filename. Refer to the Tenant Connector Reference Guide.

To create a Built-In VPN Connection:

1. Navigate to **Tenant Connector**.
2. Open the **Connector Sites** tab.
3. Click the **Add **button, enter the remote site name and description, and click **Save**.
4. Open the **Connector Node** tab.
5. Click the **Add** button and select the Built-In VPN option.
6. Select the remote site name, enter the node name, tunnel port, connection port, connector node external IP, the SSH RSA Key created during the connector node installation, and click **Save**.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/OY4-8Du8aqHtzaQ7tGPd6_image.png" size="74" width="938" height="433" caption="Built-In VPN Configuration Screen" position="center" showCaption="true"}

### Connector Monitoring

Connectors send heartbeat messages to Single Connect servers at regular
intervals. This information can be used to monitor whether the connectors are
working properly.

To check the heartbeat messages:

1. Navigate to** Tenant Connector**.
2. Open the **Connector Nodes** tab.
3. Click the **List view** button, select the connector node, and click the **Heartbeat** button.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/3L_jtJgyPYVKgEFJH1XES_image.png" size="74" width="783" height="355" caption="Connector Heartbeat Chart" position="center" showCaption="true"}

### Adding a Device to a Connector Site

In order to access the devices located at remote data centers through the
connector, these devices must be associated with the connector sites. 

To associate a device with a connector site:

1. Navigate to **Device Management** >** Device Inventory**.
2. Click the** New Device Discovery** button.
3. Fill out the relevant device information, select the connector site, and save by clicking **Discover** and **Add**.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/hJGBoKW7M5xuUymTflIMJ_image.png" size="74" width="687" height="413" caption="Adding Device to a Connector Site" position="center" showCaption="true"}

### Adding SAPM accounts

If you haveaconnector in your environment, everySAPMaccountrequest(check password, reset password etc.)isrun overthe connectorserver.The connector supports WinRM, SSH, SSH-Keys,LDAPSand databases(e.g., MySQL, Oracle, Teradata).

Some accounts (for example: AD/LDAPS, MySQL)need to edit on SAPM Configuration.

| **LDAPS ** | AD hostname with FQDN, ${devicePort}  | ldaps\://windows-server0.krontech.test:${devicePort} You must add connector IP in the hosts file of SC. example(192.168.0.1 windows-server0.krontech.test)  ldap.port   636  |
| --------------- | ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **MySQL ** | ${deviceIP}, ${devicePort}       | jdbc\:mysql://${deviceIp}:${devicePort}/testdb                                                                                                                          |

### LDAP/AD Integration via Connector Site

Enter the related configuration parametersand select the Connector Site name on LDAP Advanced filterthenclick the **Save** button.

Refer to [LDAP/AD Integration](docId:9eXGRsST2RuitTey7dW6v) 

### SIEM Integration via Connector Site

Add the parameter name is **syslog.connector.sitename **and value is your connector site name in the System Config Man.

Refer to [SIEM Configuration](docId\:aLSiKgfEsnWY5jlGm3Sda)