---
title: Making RDP/SSH/HTTP/Container Based Sessions via Kron PAM Desktop Client Application
slug: kronpam-end-user-guide-3-9-0/making-rdpsshhttpcontainer-based-sessions-via-kron-pam-desktop-client-application
description: Learn how to log in to a target device using Kron PAM Desktop Client with these simple steps. Enter your username, password, and select the server. Find the target device in the Device Group tab, double-click to connect. Navigate effortlessly with Go Forw
docTags: 
createdAt: 2022-08-12T15:00:46.000Z
---

Follow the steps below to log in to your target device via Kron PAM Server:

1. Open the Kron PAM Desktop Client Application.
2. Enter your **Username** and **Password**, select the **Server, **and **Login.**

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/1PxRCCvMJZ2Zwddn2s7-T_image.png" size="38" width="381" height="727" position="center" caption="Log in to the Kron PAM Server" darkWidth="381" darkHeight="727" showCaption="true"}

:::hint{type="info"}
To list RDP/SSH/HTTP devices and make sessions on them via the Kron PAM Desktop Client Application, the user has to have at least **single.connect.rdp.client.moduleVisibility**, ** single.connect.cli.client.moduleVisibility **and** desktop.device.group.moduleVisibility **portal functions. These three portal functions allow users only to list devices and make sessions on the Kron PAM Desktop Client, but not on Kron PAM Web GUI. 



If the users have to use both Kron PAM Desktop Client Application and Kron PAM Web GUI in this sense, the user has at least **single.connect.rdp.client.moduleVisibility**,** single.connect.cli.client.moduleVisibility, netright.discovery.moduleVisibility **and **aioc.device.group.moduleVisibility **portal functions.



Here are all possibilities and their outcomes:

**1) single.connect.rdp.client.moduleVisibility && single.connect.cli.client.moduleVisibility**
Web GUI: no device list, DC: no device list
**2) single.connect.rdp.client.moduleVisibility && single.connect.cli.client.moduleVisibility && netright.discovery.moduleVisibility**
Web GUI: device list appears & NO edit device, DC: no device list
**3) single.connect.rdp.client.moduleVisibility && single.connect.cli.client.moduleVisibility && aioc.device.group.moduleVisibility**
Web GUI: device list appears & NO edit device, DC: device list appears
**4) single.connect.rdp.client.moduleVisibility && single.connect.cli.client.moduleVisibility && netright.discovery.moduleVisibility && aioc.device.group.moduleVisibility**
Web GUI: device list appears & YES edit device, DC: device list appears
**5) single.connect.rdp.client.moduleVisibility && single.connect.cli.client.moduleVisibility && desktop.device.group.moduleVisibility(NEW)**
Web GUI: no device list, DC: device list appears
**6) single.connect.rdp.client.moduleVisibility && single.connect.cli.client.moduleVisibility && desktop.device.group.moduleVisibility(NEW) && netright.discovery.moduleVisibility**
Web GUI: device list appears & NO edit device, DC: device list appears
**7) single.connect.rdp.client.moduleVisibility && single.connect.cli.client.moduleVisibility && desktop.device.group.moduleVisibility(NEW) && netright.discovery.moduleVisibility && aioc.device.group.moduleVisibility**
Web GUI: device list appears & YES edit device, DC: device list appears
:::

*(Optional*) If the **desktop.client.otp.enabled **system config parameter is set as **true** and if the Multi-factor Authentication (OTP) is enabled for the user, the Kron PAM Desktop Client asks the user to enter his/her authentication token to finalize the authentication process.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/7bIOMon2gsyZNpbU3VueG_image.png" size="50" caption="Enter the OTP to Log in to the Kron PAM Server" isUploading="false" width="788" height="1519" darkWidth="788" darkHeight="1519" showCaption="true"}

- From the **Device **tab, press the **Make a Connection** button on the far right of the target server.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/9m9xtEkAQI_AXdI9WEaM7_image.png" size="38" width="345" height="661" position="center" darkWidth="345" darkHeight="661" showCaption="false"}

- After pressing the **Make a Connection** button, the session will be opened.

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/PsfLCQzc1kkQrjbF7rl7J_image.png)

:::hint{type="info"}
Kron PAM Desktop Client Application uses its own idle session timeout, separate from the Kron PAM Web GUI idle timeout. Your Kron PAM administrator sets this value using the *aioc.desktop.client.session.idletime.minute* system config parameter. If this parameter is not defined, Kron PAM Desktop Client uses a default idle timeout of **20** minutes.
:::