Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Updating the robotics configuration files for single sign-on authentication through Kerberos

Updated on January 31, 2022

Update the common configuration settings to authenticate attended robots and package publish requests in Pega Robot Manager through Kerberos.

The CommonConfig.xml file stores the settings that specify the authentication method and drive the connection and between your robotic solution and Pega Robot Manager. For more information about the CommonConfig.xml file, see Common configuration settings.

  1. Open the CommonConfig.xml file in a text editor of your choice.
    Typically, the file is in the C:\ProgramData\Pegasystems directory.
  2. In the Servers section, for the RobotManager server object, define the following details:
    1. Set the enabled attribute to true.
    2. Set the authenticationType attribute to Kerberos.
    3. Set the baseURL attribute to the Pega Platform URL on which Pega Robot Manager is installed and ensure that the URL ends with prweb.
      For example, http://www.MyPegaPlatformServer.com/prweb
    4. Specify your deployment type by setting the RPA attribute.
      The following values are available:true – Unattended (RPA)false – Attended (RDA)
    For example:
    <Server name=”RobotManager” enabled=”true” baseURL=https://MyPegaServer.com/prweb 
    RPA=”false” workgroup=”Savings accounts” robotName=”{MachineName}”
    authenticationType=”Kerberos” RPAServiceOperator=”ACME.RPA_Service” />
What to do next: Users that you add through the Pega Robot Manager interface are automatically associated with an authentication method, based on their role and the values in specific dynamic system settings. Before adding users, either manually or through import, specify the default authentication method that is assigned to each user role.

For more information, see Specifying the default authentication method for new Pega Robot Manager users.

    • Previous topic Configuring Apache Tomcat to support Kerberos/SPNEGO authentication for Pega Robot Manager users
    • Next topic Specifying the default authentication method for new Pega Robot Manager users

    Have a question? Get answers now.

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

    Did you find this content helpful?

    Want to help us improve this content?

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

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us