---
title: Tenant Connector Outbound Installation
slug: kron-pam-installation-guides-v3/tenant-connector-outbound-installation
docTags: 
createdAt: 2025-06-03T07:33:37.449Z
---

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/t2KSt_nu2RQbA2xN6s358_image.png "The Tenant Connector Outbound Option")

:::hint{type="warning"}
Check the Secure Boot Enabled status before the installation by running the **`mokutil --sb-state`** command.
In case secure boot is enabled, it might cause an error during the WireGuard installation. **Please disable it to continue the installation!**
:::

The following steps should be read carefully to successfully install Tenant Connector Outbound on the regarding machine:

- Download the installation script on the machine that is used for Tenant Connector Outbound. The support team can provide the installation script. After downloading the script, unzip the installation script on the machine. The user can use the unzip command to extract the files from the installation script file.

:::hint{type="info"}
In case the **bash: unzip: command not found **error is shown, the unzip package needs to be installed via the **sudo dnf install -y unzip** command.
:::

:::BlockQuote
Linux CLI: \[root\@connector\~]# unzip RAP\_MTC\_ONCLOUD-1.4.0.zip
:::

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/azhsxamzhNtog1tSPVAys_image.png "Extracting the zipped installation script files")

:::hint{type="info"}
If somehow the user needs to start the script again (maybe because of the wrong input or missing file, etc), please remove all installation files except for the compressed installation script file and unzip the compressed installation script file again. After this, you can execute the script.

**We highly recommend this method, since the extracted files might be modified after the script execution for the first time, and executing the script with modified files might cause the problematic installation!**
:::

- Navigate to the cloud directory:

:::BlockQuote
Linux CLI:	\[root\@connector\~]# cd cloud
:::

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/kzcB2Z_c2tzDbnPNNU6qg_image.png" size="52" width="524" height="117" position="center" caption="Navigating the cloud directory" darkWidth="524" darkHeight="117" showCaption="true"}

- Run the configuration script:

`Linux CLI:	[root@connector~cloud]# sh configure.sh`

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/fMqyQ2foKwzLT-5cFhL1d_image.png" size="58" width="633" height="212" position="center" caption="Starting the installation script" darkWidth="633" darkHeight="212" showCaption="true"}

:::hint{type="info"}
In case you need to set script permissions to execute it, you need to run the**`chmod +x configure.sh `**command**.**
:::

:::hint{type="info"}
You should have root privileges to run this script.
:::

- The installation script should be restarted after the forced reboot. The installation script asks the user to either:
  a) install MT Outbound Connector on the cloud, or b) install MT Inbound Connector, or to install the Secure Remote Access Portal (RAP) module on the cloud. (The last option is not related to MT Connector.)

:::hint{type="warning"}
If you have see this problem during the installation: 

Errors during downloading metadata for repository 'appstream':

  \- Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https\://mirrors.rockylinux.org/mirrorlist?arch=x86\_64\&repo=AppStream-8 **\[SSL certificate problem: certificate is not yet valid]**



**Please check the system clock and sync the clock time:**

systemctl enable chronyd --now

chronyc -a makestep
:::

- To continue with the Tenant Connector Outbound installation, the user should select the first option by** entering 1 and pressing the Enter key.**

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/UqqoMpJ_KC9iq303djqDA_image.png "Selecting Install MTC - Outbound")

- Once the** Installation is completed, leaving …** message is seen on the screen, the installation is finalized.

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/p21jhSjvWF1yCjEGq3Sio_image.png "The end of the installation script")

- The rest of the configuration (WireGuard, pam-connector.service, etc) is handled in the process of adding an outbound connector node by pressing the** SAVE **button after filling in all required data on the Tenant Connector page of Kron PAM Web GUI.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/fg57qfTUaS6dYoLUkKQl-_image.png" size="78" width="756" height="661" position="center" caption="Tenant Connector Outbound Configuration on the Kron PAM Web GUI" darkWidth="756" darkHeight="661" showCaption="true"}

:::hint{type="info"}
You can find the status of the rest of the configuration management mentioned in the 8th step by checking the **connector.log** file under **/pam/gui/logs**. In case you see a **Success** message at the end of the log file, the installation is completed.
:::

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/gs4LVN7BAKunUPuKazTBv_image.png "The tenant connector is ready to be used")