PRA Site Selection Behavior

When launching a session in Privileged Remote Access (PRA), the system can automatically select a Platform Engine site based on the default site configuration of a secret. If the name of a Platform Engine site matches the default site name set on a secret, the PRA workload on a Platform Engine within that site will be automatically used for the session. This eliminates the need to manually select a site.

Example Scenario

Consider a scenario where you have a Platform Engine site named Default and a Secret Server or Distributed Engine site also named Default, configured as the secret's default site. In this case, a PRA workload will be automatically selected from the pool of Platform Engines deployed to the Default site, facilitating the user's remote connection without any additional site-selection prompts.

Handling Non-Matching Sites

If there is no matching site name or if no Platform Engines with PRA workloads are deployed to the matching site, users will be prompted to select an appropriate site to facilitate the connection. This ensures that the connection can still be established even if automatic site selection is not possible.. See Managing Engine Sites and Secret Server sites for more information.