RDCMan-plugin Implementation Guide-V2.9 Release
RDCMan-plugin Implementation Guide-V2.9 Release
Manager
PSM Plugin
Implementation Guide
2.9
CYBERARK Implementation Guide
2 Solution Overview............................................................................................... 3
3 Plugin Installation ............................................................................................... 4
3.1 Pre-Requisites 4
3.2 Installation Steps 5
3.3 First Run of Remote Desktop Connection Manager 5
www.cyberark.com Page 1 of 13
CYBERARK Implementation Guide
1 DOCUMENT PROPERTIES
The content of this document is provided for informational use only. This document is presented "as-
is" and material contained in this document, including screen captures, URLs, and other website links
or references may change. In addition, the actual user experience and success of this tool may hinge
on unique customer environment variables and system settings, such as operating system, network
access, safe and platform design, etc..
1.2 Terms
This tool provided as a "Community" solution. Please refer to "CyberArk Marketplace Terms of Use"
for further information.
www.cyberark.com Page 2 of 13
CYBERARK Implementation Guide
2 SOLUTION OVERVIEW
The PAMPlugin is a lightweight integration for Remote Desktop Connection Manager (RDCMan)
leveraging the CyberArk Password Vault Web Access (PVWA) REST API. It enables users to create
and manage a list of systems they wish to connect to while at the same time using CyberArk to
isolate and obviate credentials. This allows users to transparently connect to targets via the PAM
solution.
www.cyberark.com Page 3 of 13
CYBERARK Implementation Guide
3 PLUGIN INSTALLATION
3.1 Pre-Requisites
▪ Regular access via your least privileged account to logon to and authenticate to the PVWA
Server as well as access to view your accounts.
▪ Any version of Windows (tested on Windows 10)
o .NET Framework deployed (uses v4.7)
▪ Microsoft Remote Desktop Connection Manager (tested Version 2.90.1420.0)
▪ Requires 443 access to the PVWAs.
▪ Requires 3389 access to Privileged Session Manager (PSM) server.
▪ Supports all Authentication Methods that are supported by CyberArk PVWA API:
o CyberArk
o SAML (Simple Authentication Markup Language)
o LDAP (Lightweight Directory Application Proto col)
o RADIUS (Remote Access Dial In User Service)
o PKI (Public Key Infrastructure) and PKI PN (PKI Principal Name)
▪ NOTE: CyberArk recommends using MFA for all authentication as referenced in Security
Fundamentals.
www.cyberark.com Page 4 of 13
CYBERARK Implementation Guide
Figure 1
Figure 2
www.cyberark.com Page 5 of 13
CYBERARK Implementation Guide
www.cyberark.com Page 6 of 13
CYBERARK Implementation Guide
Figure 3
▪ Click “Finish” to proceed. Review the new capabilities and menus available in RDCMan and
click “Start.”
www.cyberark.com Page 7 of 13
CYBERARK Implementation Guide
4 APPLICATION MANAGEMENT
Figure 4
www.cyberark.com Page 8 of 13
CYBERARK Implementation Guide
5 PLUGIN USAGE
Right-click on a target server and navigate to the “Connect server via CyberArk” dropdown menu.
(See Figure 5)
Figure 5
Figure 6
www.cyberark.com Page 9 of 13
CYBERARK Implementation Guide
Figure 7
Figure 8
The user can review the request status from the PAM Menu at the top of the RDCMan window.
Figure 9
www.cyberark.com Page 10 of 13
CYBERARK Implementation Guide
Figure 10
Figure 11
www.cyberark.com Page 11 of 13
CYBERARK Implementation Guide
6 SECURE DLL
To secure the usage of this DLL, CyberArk recommend using EPM to validate the hash of the DLL.
For more information, contact your CyberArk Representative.
www.cyberark.com Page 12 of 13