Skip to main content


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

Selecting the Kerberos method for authenticating Pega Robot Manager users

Updated on December 20, 2022

Determine the Kerberos method for authenticating traffic to Pega Robot Manager by configuring the EnableDefaultKerberosAuthenticationForRobotManger dynamic system setting.

You can use the built-in capability that provides support for third-party SPNEGO libraries, or you can use your own method of Kerberos authentication. This guide focuses on the setup process with the SPNEGO libraries, because this is one of the most commonly used methods.
Before you begin: Configure either a SPNEGO library, or configure a custom Kerberos authentication method, in accordance with your security policy. For more information on how to configure the SPNEGO libraries and Tomcat, see Configuring Apache Tomcat to support Kerberos/SPNEGO authentication for Pega Robot Manager users.
  1. In the navigation pane of Dev Studio, click RecordsSysAdminDynamic System Settings.
  2. Select the EnableDefaultKerberosAuthenticationForRobotManger dynamic system setting.
    Note: You can quickly search for dynamic system settings by filtering them by their Setting Purpose property, as shown in the following example:
    Filtering dynamic system settings in Dev Studio
    Using the Setting Purpose filter to find a dynamic system setting in Dev Studio
  3. On the Settings tab, in the Value field, enter one of the following values:
    • true – Select this option if you are using the in-build Kerberos authentication method through SNEGO libraries.
    • false – Select this option if you are using another Kerberos authentication method.
    See the following figure for reference:
    Specifying the Kerberos authentication method
    Configure the EnableDefaultKerberosAuthenticationForRobotManger to determine the supported Kerberos authentication method
  4. Confirm your settings by clicking Save.
What to do next: Update the robotic automation configuration files to enable single sign-on authentication of Pega Robot Runtime and client requests from Pega Robot Studio in Robot Manager.
    • Previous topic Configuring Pega Robot Manager to use Kerberos authentication
    • Next topic Configuring Apache Tomcat to support Kerberos/SPNEGO authentication for 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