Configuring the CommonConfig.xml file for BeyondTrust
Prepare a robot for integration with BeyondTrust and to store shared secrets by
editing the CommonConfig.xml file.
To configure a robot to integrate with BeyondTrust, perform the following
steps:What to do next: To complete the robot setup for BeyondTrust, configure the
- Open the
CommonConfig.xmlfile in a text editor. - In the
CommonConfig.xmlfile, modify the RobotManager and the CredentialManager elements to integrate Pega Robotic Automation with BeyondInsight and Password Safe.BeyondInsight is a BeyondTrust offering that provides centralized management, reporting, and threat analytics for their Privilege Access Management module.The RobotManager element controls whether the computer is an unattended robot (RPA="true") or an attended robot (RPA="false"). External credential providers are only available for unattended robots, so set this element to true, as shown in this example:<Server name=”RobotManager” baseURL=”http://[server-redacted]:9080/prweb” enabled=”true” proxyAddress=”” RPA=”true” authenticationType=”Basic” RPAServiceOperator=”RPA_{MachineName}” workgoup=”Credit Cards” robotname=”{MachineName}” suppressNotificationsForRPA=”true” /> - In the
CommonConfig.xmlfile, locate the CredentialManager element. This element controls whether the system uses an external credential provider (enabled = “true”), and which credential provider is active (providerType = “BeyondTrust”). If you do not enable an external credential provider, the system uses the default local DPAPI credential provider. The following is an example of how you should set this element for BeyondTrust:<Server name=”CredentialManager” baseURL=”” enabled=”true” mappingFileLocation=”CommonApplicationData” providerType=”BeyondTrust” /> - Save and then close the
CommonConfig.xmlfile.
CredentialManagerConfig.xml file.Previous topic BeyondTrust examples that include replaceable parameters Next topic Configuring the CredentialManagerConfig.xml file for BeyondTrust