Skip to main content

Table of Contents

Configuring Pega Robot Runtime for RPA mode to support Basic authentication

Complete the following steps so that Basic authentication is supported in Pega Robotic Automation Runtime when running RPAs.

  1. In Pega Platform, configure the DefaultAuthenticationTypeForRuntimeOnlyUser Dynamic System Setting to have the value Basic.

    For detailed information, see the Configuring authentication for Pega Robot Manager.
  2. Configure the CommonConfig.xml file:

    1. In the Servers section, find the server element with the name RobotManager.

      For example, <Server name="RobotManager" enabled="true" baseURL="" RPA="true" workgroup="My Group" robotName="{MachineName}" authenticationType="Basic"/>.
    2. Set the enabled attribute to true.

    3. Set the authenticationType attribute to Basic or empty.

    4. Set the baseURL attribute to the Pega Platform URL on which Pega Robot Manager is installed and ensure that it ends in prweb.

      For example,
    5. Set the RPA attribute to true.

    6. Set the robotName attribute to the pattern that you want to use for your RPA virtual machine (VM) names.

    7. Set the workgroup attribute to the name of the workgroup into which robotic virtual machines register.

    8. In the Servers section, find the Server element with the name IdP or ADFS.

    9. Set the enabled attribute to false.

    10. If there are entries for both servers, delete the ADFS element, because it is deprecated.

  3. Configure the RuntimeConfig.xml file by setting the Robotics/PackageServer/baseUrl attribute to use the Pega Robotic Automation Package Server URL for package deployment.

  4. Start Pega Robotic Automation Runtime.

    You will be prompted to enter the credentials of the administrative operator (Dispatch Operator) who has the appropriate access role to register VMs such as PegaRULES:RoboticAdministrator.

  • Pega Robot Manager authentication mechanisms

    Pega Robot Manager supports Basic authentication, OAuth 2.0 with SAML bearer, and Kerberos to authenticate client requests from Pega Robotic Automation Studio and Pega Robotic Automation Runtime.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us