Updating the robotics configuration files for basic authentication
Update the common configuration settings to authenticate attended or unattended robot operators and package publish requests in Pega Robot Manager by using the basic method.
The CommonConfig.xml
file stores the settings that specify the
authentication method and drive the connection between your robotic solution and
Robot Manager. For more information about the
CommonConfig.xml
file, see Common configuration settings.
- Open the
CommonConfig.xml
file in a text editor of your choice.Typically, the file is in theC:\ProgramData\Pegasystems
directory. - In the
Servers
section, for theRobotManager
server object, define the following details, depending on your deployment type:Choices Actions Attended - Set the
enabled
attribute to true. - Set the
authenticationType
attribute to Basic or leave empty. - Set the
baseURL
attribute to the Pega Platform URL on which Robot Manager is installed and ensure that the URL ends with prweb.For example, http://www.MyPegaPlatformServer.com/prweb - Set the
RPA
attribute to false.
Unattended - Set the
enabled
attribute to true. - Set the
authenticationType
attribute to Basic or leave empty. - Set the
baseURL
attribute to the Pega Platform URL on which Robot Manager is installed and ensure that the URL ends with prweb.For example, http://www.MyPegaPlatformServer.com/prweb - Set the
RPA
attribute to true. - Set the
robotName
attribute to the pattern that you want to use for your robot operator names.For example, to name the robot the same as the machine on which it resides, setrobotName
to {MachineName}. - Set the
RPAServiceOperator
attribute to the pattern that you want to use for your RPA service operator name.For example,ACME.RPA_Service
.
For example: The following code snippet provides an example configuration when using unattended robots: <Server name=”RobotManager” enabled=”true” baseURL=https://MyPegaServer.com/prweb RPA=”true” workgroup=”Savings accounts” robotName=”{MachineName}” authenticationType=”Basic” RPAServiceOperator=”ACME.RPA_Service” />
Note: Do not configure the workgroup
parameter in theCommonConfig.xml
file. Instead, configure the work group assignment in Robot Manager. For more information, see Robot registration and work group assignment for RPA (unattended) robots. - Set the
- In the
Servers
section, for the server object whoseServer name
is IdP, ensure that theenabled
attribute is set to false. - Save the file.
- For robotic deployments that include Pega Robot Studio,
configure the
StudioConfig.xml
file by setting theRobotics/PackageServer/baseUrl
attribute to use the Pega Robotic Automation Server URL for package deployment.StudioConfig.xml
contains configuration settings for Pega Robot Studio. For more information, see Studio configuration settings. - Configure the
RuntimeConfig.xml
file by setting theRobotics/PackageServer/baseUrl
attribute to use the Pega Robotic Automation Package Server URL for package deployment.Important: Edit the RuntimeConfig.xml
file only in Robot Manager. Any edits that you make directly in the file by using a text editor are overwritten when Pega Robot Runtime starts. For more information, see Managing robot configuration remotely.
For more information, see Specifying the default authentication method for new Pega Robot Manager users.
Previous topic Authenticating Pega Robot Manager users through the basic method Next topic Understanding single sign-on authentication for Pega Robot Manager users