PAM360 Remote Connect

PAM360 Remote Connect is an independent desktop client for Windows that is designed to help you launch direct remote connections via password-less login to Windows and SSH-based target resources without needing to install multiple remote clients or a web browser. To achieve this, Remote Connect utilizes the PAM360 server's API to act as a stand-alone client for remote connections that is independent of the PAM360 web application. PAM360 Remote Connect ensures seamless operation of the authentication and remote access mechanisms for RDP, SSH, and thick-client SQL connections. Essentially, it acts as both the Microsoft Terminal Services Client (MSTSC) and SSH PuTTY client rolled into a single, lightweight application with auditing capabilities.

To learn how to configure the PAM360 Remote Connect application in a user endpoint and attain remote sessions from it, refer to this help documentation.

By the end of this document, you will understand the benefits, key features, current limitations, and troubleshooting tips of PAM360 Remote Connect.

1. Benefits of Using PAM360 Remote Connect
2. PAM360 Remote Connect Features
3. Limitations of PAM360 Remote Connect
4. Troubleshooting Tips

1. Benefits of Using PAM360 Remote Connect

• PAM360 Remote Connect offers password-less, one-click login for seamless access to remote endpoints.
• Remote Connect is a lightweight client, capable of launching both RDP and SSH-based connections from a single interface—thus eliminating the need to install multiple applications to get the job done.
• Remote Connect can launch concurrent active remote connections in multiple tabs.
• SSH-based remote sessions initiated via Remote Connect are highly customizable. The client allows you to modify system settings within the remote session window and lets you perform operations that you can carry out on a local machine, such as opening the session window in full screen and changing the keyboard configurations. This provision helps elevate the overall user experience.

2. PAM360 Remote Connect Features

1. SSH Proxy: PAM360 Remote Connect supports remote access even when direct connectivity between the source machine and target endpoints is unavailable. By configuring an SSH Proxy, users can establish secure remote sessions with just a connection between the source machine and the PAM360 server. This eliminates the need for direct RDP/SSH access from user workstations to endpoints, enhancing flexibility and security. To learn about configuring the SSH Proxy for remote sessions in the PAM360 Remote Connect application, refer to this help documentation.
2. Application Credential Injection: PAM360 supports automatic password injection in third-party thick-client applications to establish connections to database servers directly from the PAM360 Remote Connect desktop client. Refer to this help documentation for more information.

3. Limitations of PAM360 Remote Connect Features

• As of now, PAM360 Remote Connect does not support session recording, session monitoring, and termination. Please access PAM360's web interface to avail the product's extensive PSM features.
• As of now, advanced connection settings configured for remote connections in the PAM360 web application will not apply to the remote sessions launched via Remote Connect.
• The Secure File Transfer Protocol (SFTP) option is not available in the Remote Connect interface. However, direct file transfer will work between machines once the RDP/SSH connection is established.
• As of now, Remote App support is not available. If Remote App is configured for any resource, users will not be able to connect to it via Remote Connect.
• Once an end-user has launched a remote connection via Remote Connect, resource owners cannot terminate the session from the PAM360 web server.
• Launching remote connections using the currently logged in Active Directory/Microsoft Entra ID/LDAP account credentials are not available for now.
• The Ctrl+Alt+Del option will not work in an RDP session initiated via Remote Connect.
• The minimize option on the RDP session console, displayed after entering full-screen mode, will not function in an RDP session initiated via Remote Connect.