Getting Started With PRA

PRA connections enable secure, VPN-less, browser-based access to remote machines. The PRA service automatically injects vaulted credentials to connect users with their target resources without exposing the credentials to the end-user.

Setting Up Privileged Remote Access (PRA)

Prior to using PRA for the first time in the Delinea Platform, you need to deploy some key components of the solution.

The basic initial setup for PRA requires an administrator to carry out these steps:

1. Deploy a Platform Engine with a PRA Workload

The core deployment for PRA involves installing a Platform Engines on a host machine within the corporate network that runs a PRA Workload.

  • Navigate to Engine Management: Access the Engine Management page (which can be found through global search or under Settings.)

  • Create a Site: A site acts as a logical grouping or network demarcation for the engines. Engines deployed to a site, must have network connectivity to all assets on that site. See Managing Engine Sitesfor more information.

  • Deploy a Platform Engine: After creating a new site (or selecting an existing site), navigate to the Engines tab and deploy a Platform Engine. See Adding a Platform Engine for more information.

  • Engine Function: Once installed and active, the Platform Engine connects with the Delinea Platform and is ready to host brokered connections to target systems.

2. Launching a PRA Session

  • Ensure launch permissions: Ensure you have all the necessary permissions to launch a remote connection to a target resource. See Remote Access Permissions for more information.

  • Launch from a vaulted credential: Use a secret with credentials in the integrated Secret Server vault to launch a remote connection. See Launching a PRA Session for more information.

  • Launch from the Inventory: Alternately, you may launch a remote connection to a target asset that has been discovered and populated into the Platform Inventory. See Inventory for more information.